← Docs

Docs · Connector reference

Salesforce connector reference

Operations, inputs, troubleshooting, and questions for the Salesforce connection. Policy decides each change before the credential is resolved, and the action record carries the result.

Set up and verify the Salesforce connection

  1. Choose one task and its account, and match the reads and actions on the overview page to it before granting provider permissions.
  2. Prepare the connection settings from the overview page, connect the provider in Deixic, and choose which tools your agent can use.
  3. Try a small task with a known result, and compare the returned identity and resource with what the account owner expects.
  4. Configure approval for sensitive changes, review the destination and inputs, and check the result in the provider before expanding the workflow.

Information your agent can use

ResourceRecord identityStart withPage coverage
AccountsIdTop levelNext-page URL
ContactsIdTop levelNext-page URL
Record identity
Match on these fields before joining or deduplicating results; where none is specified, check the returned record first.
Start with
Resolve the parent identifier first.
Next-page URL
Next-page URL. Follow the continuation returned by the provider before treating the collection as complete.

Supported operations

Review the inputs before granting an action to an agent. Required inputs must be supplied, optional inputs narrow the request, and provider permissions apply in addition to Deixic policy.

Read
Retrieves information; check the returned scope and identifiers before use.
Action
Can change provider state; review the target and inputs, then retain the result to avoid repeating completed work.
OperationEffectApprovalProvider permissionsInputs
Accounts SearchReadBy policyapi2
Contacts SearchReadBy policyapi2
Account CreateActionApproval requiredapi4
Account UpdateActionApproval requiredapi5
Contact CreateActionApproval requiredapi5
Contact UpdateActionApproval requiredapi6
Account GetReadBy policyapi1
Account RenameActionApproval requiredapi2

Inputs by operation

Accounts Search Read
Inputs for Salesforce Accounts Search
InputRequirementAccepted value
limitOptionalintegerMinimum: 1Maximum: 100
queryOptionalstringMinimum characters: 1Maximum characters: 128
Contacts Search Read
Inputs for Salesforce Contacts Search
InputRequirementAccepted value
limitOptionalintegerMinimum: 1Maximum: 100
queryOptionalstringMinimum characters: 1Maximum characters: 128
Account Create Action · approval required
Inputs for Salesforce Account Create
InputRequirementAccepted value
industryOptionalstringMaximum characters: 255
nameRequiredstringMinimum characters: 1Maximum characters: 255
phoneOptionalstringMaximum characters: 64
websiteOptionalstringMaximum characters: 2048
Account Update Action · approval required
Inputs for Salesforce Account Update
InputRequirementAccepted value
industryOptionalstringMaximum characters: 255
nameOptionalstringMinimum characters: 1Maximum characters: 255
phoneOptionalstringMaximum characters: 64
record_idRequiredstring
websiteOptionalstringMaximum characters: 2048
Contact Create Action · approval required
Inputs for Salesforce Contact Create
InputRequirementAccepted value
account_idOptionalstring
emailOptionalstringMaximum characters: 320
first_nameOptionalstringMaximum characters: 255
last_nameRequiredstringMinimum characters: 1Maximum characters: 255
phoneOptionalstringMaximum characters: 64
Contact Update Action · approval required
Inputs for Salesforce Contact Update
InputRequirementAccepted value
account_idOptionalstring
emailOptionalstringMaximum characters: 320
first_nameOptionalstringMaximum characters: 255
last_nameOptionalstringMinimum characters: 1Maximum characters: 255
phoneOptionalstringMaximum characters: 64
record_idRequiredstring
Account Get Read
Inputs for Salesforce Account Get
InputRequirementAccepted value
record_idRequiredstring
Account Rename Action · approval required
Inputs for Salesforce Account Rename
InputRequirementAccepted value
NameRequiredstringMinimum characters: 1Maximum characters: 255
record_idRequiredstring

When the Salesforce task does not produce the expected result

Connected, but the expected data is missing

Check the identity behind the oauth connection and its access to the specific resource; a successful connection does not establish access to every object.

Compare the lookup against one known record first, and keep an empty response separate from a permissions error.

The answer covers only part of the data

Check the resource’s page coverage, query filters, and result limit, and have the agent state the account and time window it inspected, so a partial response yields a scoped answer.

The agent keeps doing the same work

Inspect the action history for repeated targets and inputs, keep the successful result’s identifiers with the task, and refresh a lookup only when the information changed.

A change is waiting or failed

Check whether the call awaits approval, was rejected by policy, lacks an input, or failed at the provider, and after a timeout inspect the destination before repeating a write.

See how an action proceeds and how to review an approval.

Questions about the Salesforce connector

Can I use my existing agent with Salesforce?

Yes: connect your agent to Deixic through MCP, choose which connected tools it can use, and Deixic checks calls routed through its gateway; Dex is available if your team also wants an agent.

Can an agent change data in Salesforce?

This connector supports 2 actions, listed on its overview page. Configure a connection and choose the tools and provider permissions your task needs; an available action is not permission for every agent to run it, and Deixic policy and any required approval still apply to calls through the gateway.

What do I need to connect Salesforce?

Prepare Salesforce instance URL, OAuth client ID, OAuth client secret, OAuth access token; the connection uses OAuth, and the connected identity’s provider permissions determine which resources it can access.

Does connecting Salesforce keep every answer up to date?

No: an earlier answer is still an earlier answer, so for a decision that depends on current state, have the agent refresh the source and retain the lookup time, and save stable instructions separately from facts that can change.