Setup takes four steps: set up an app in Salesforce, connect it in Invoca, configure your fields, and attach the skills to your agent.
This integration is separate from the Invoca for Salesforce app that adds call data after a call. You can use both; they use separate credentials.
Before you begin
- Salesforce is enabled on your Invoca account. If you don’t see Salesforce in Manage Integrations, contact Invoca.
- Your Salesforce edition includes hosted MCP servers. Salesforce includes them with Enterprise Edition and above.
- A Salesforce admin is available. Setup requires Salesforce Setup access to create an External Client App and turn on MCP servers.
- You’ve chosen the Salesforce user the agent acts as. The agent can only see and change what that user can. Give that user access to Leads, Events, Accounts, and Cases as needed.
- Sandbox first (optional). You can connect a Salesforce sandbox for testing, then connect production when you’re ready.
Connect Salesforce
You connect by creating an External Client App in Salesforce, then signing in from Invoca. Invoca never sees or stores your Salesforce password. In Salesforce (admin):- In Setup, go to API Catalog > MCP Servers and turn on Salesforce’s hosted MCP servers.
- Create an External Client App. Connected Apps aren’t supported.
- In its OAuth settings, enter the callback URL your Invoca team gives you, and add the scopes for hosted MCP access (
mcp_api) and offline access (refresh_token). - Require PKCE, turn on JWT-based access tokens, and turn off the requirement for a client secret.
- Copy the app’s Consumer Key. New apps can take up to 30 minutes to start working.
- Open Manage Integrations and select Salesforce.
- Add a new credential and paste the Consumer Key. For a sandbox, set the login host to
test.salesforce.com, or enter your My Domain URL. - Sign in to Salesforce as the user the agent should act as, and approve access.
- Confirm the connection shows as connected.
Configure fields
The agent writes standard Salesforce fields, using their API names. Check these rules against your org before you go live:
If your org requires extra fields, or a validation rule blocks records without them, the agent’s saves fail. Relax the rule for the agent’s user, or ask your Invoca team about field mapping for your connection.
Add skills to your AI agent
- Open your agent in Agent Builder.
- Choose the action:
- For appointments, open the Schedule Appointment action.
- For lead and case updates, open any other action.
- In the skill field, choose the Salesforce skill, then choose your Salesforce connection.
- Test the agent with a test lead, then publish it.
How the agent works with Salesforce
The agent looks records up before it changes them, and only says something was saved after Salesforce confirms it. It confirms the date and time with the caller before booking, rescheduling, or canceling an appointment.
Salesforce doesn’t tell the agent which times are open, so the agent books the time the caller asks for. Add your business hours and booking rules to the agent’s instructions so it only offers times you can serve. The agent speaks times in the caller’s timezone.
Data and privacy
- Salesforce permissions apply. The agent acts as the user who connected, so your profiles, permission sets, and sharing rules limit what it can see and change.
- No reading back stored data. The agent only confirms details the caller gave, and never shares other people’s records.
- No made-up results. The agent only says a record was saved or an appointment booked after Salesforce confirms it.
- No internal details. The agent doesn’t say record IDs, field names, or system terms to the caller.
- You stay in control. To stop access, remove the connection in Manage Integrations, or revoke the External Client App in Salesforce.
Limitations
- No availability check. Salesforce has no open-times lookup, so the agent can’t check a rep’s calendar before booking.
- Standard fields only. Custom fields (ending in
__c) can’t be written. - Contacts are read-only. The agent can find contacts but creates and updates leads, not contacts.
- Canceled events stay. A canceled event remains in Salesforce, marked as canceled, rather than being deleted.
- Vague errors. Salesforce sometimes returns a general error, for example when a picklist value is rejected. Check your validation rules and picklists if saves fail.
Troubleshooting
Still stuck? Contact Invoca with the agent name and the time of the conversation.