Integrate your Salesforce org with Gemini Enterprise, so your sellers can research leads and update records inside Gemini. This single-view access equips sellers to plan strategies and close deals faster without switching between two workspaces.
To bring your Salesforce data into Gemini so your sellers can research, strategize, and close more deals, turn on the Agentforce Sales Agent for Gemini and complete the setup in Salesforce and Gemini.
Required Editions
|
Available in: Enterprise, Performance, and Unlimited editions with the Agentforce for Sales add-on. Also available with Einstein 1 Sales and Agentforce 1 Sales editions. |
|
User Permissions Needed | |
|
To set up the Agentforce Sales Agent for Gemini in Salesforce: |
Customize Application AND View Setup |
|
To give Salesforce users access to the Agentforce Sales Agent for Gemini in Salesforce: |
Customize Application AND View Setup |
|
To set up the Agentforce Sales Agent in Gemini: |
Administrator access to Gemini Enterprise, including the console URL or engine your Google Cloud administrator provides |
Turn On Agentforce Sales Agent for Gemini
From the gear icon, select Salesforce Go.
Search for Agentforce Sales Agent for Gemini (Beta).
Go to the Agentforce Sales Agent for Gemini (Beta) page and turn it on.
Create and Configure an External Client App
To create an External Client App, go to Setup. On the External Client App Manager page, click New External Client App.
Enter the app name, Gemini Integration. Add your Salesforce email, and leave the Distribution State as Local.
Open API (Enable OAuth Settings) and select Enable OAuth.
In Callback URL, add these URLs, each on a separate line:
In OAuth Scopes, select these settings:
Access Salesforce hosted MCP servers (mcp_api)
Perform requests at any time (refresh_token, offline_access)
Deselect all checkboxes in Flow Enablement.
In Security, select only these settings, and uncheck the remaining settings.
Require secret for Web Server Flow
Require secret for Refresh Token Flow
Enable Refresh Token Rotation
Issue JSON Web Token (JWT)-based access tokens for named users
Click Create.
Open your newly created ECA, and on the Settings tab, expand OAuth Settings.
Click Consumer Key and Secret. Copy and store the values securely to use later when adding the Client Id and Client Secret on the agent card in Gemini.
On the Policies tab, expand OAuth Policies. In App Authorizations, change the refresh token validity period from 365 days to 30 days and save.
NOTE: Salesforce requires that you have an access token timeout of one hour or more. Make sure your session timeout meets this requirement, or change the access token timeout in Named User JWT-Based Access Token Settings.
Give Users Access
To give users access, enter Permission in the Quick Find box, and then select Permission Sets.
Click New.
Enter a label, such as Custom Gemini Permission Set, and Save.
Return to the External Client App Manager page, and open the ECA you created.
On the External Client App Policies tab, under OAuth Policies, set Permitted Users to Admin approved users are pre-authorized.
In Select Permission Sets, add the permission set, then save.
Assign the permission set to users who want access to the Agentforce Sales Agent for Gemini.
To add the Agentforce Sales Agent in Gemini, go to Gemini from the Agentforce Sales Agent for Gemini (Beta) page in Salesforce Go.
If your company isn’t subscribed, click the Subscribe button then Go to Gemini Enterprise.
Click Apps and select your app.
Note: If you’re setting up in a sandbox org, an app specifically for your sandbox shows in the list .
Go to Agents and click Add Agent. Choose the Agents via Marketplace type.
Select Agentforce Sales Agent and review the information.
For sandbox setup only:
Replace the default Authorization URL with: https://test.salesforce.com/services/oauth2/authorize?prompt=select_account
Replace the default Token URL with: https://test.salesforce.com/services/oauth2/token
Add the Consumer Key and Secret from your Salesforce External Client App in the Gemini Client ID field and Client secret fields, and click Finish.
005318942

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.