Salesforce

The Salesforce package exposes common object operations through the local marketplace runtime. Use it for bounded access to accounts, contacts, opportunities, leads, cases, or selected custom objects.

Connect

Enter an OAuth access token or session ID and the matching Salesforce instance_url. The token and URL must belong to the same Salesforce environment.

Prefer a dedicated integration user with only the object and field permissions required for the agent’s job. Salesforce permission sets remain the upstream security boundary.

Allow object API names

The connector allowlist contains API names such as Account, Contact, Opportunity, Lead, Case, or Invoice__c. Use the exact API name, including the __c suffix for custom objects.

Do not use broad labels such as “all CRM data.” Start with one or two object types and expand after successful verification.

Read and write behavior

Read tools can search and retrieve allowed records. Write tools can create, update, or delete within the allowed object types only when connector writes are enabled and the Salesforce identity has the required Create, Edit, or Delete permission.

Leave writes unchecked by default. For an update, review object type, record ID, field API names, and new values. For deletion, require a fresh approval.

Verify

1. Query one known allowed record.
2. Attempt an unlisted object and confirm rejection.
3. Create a test record only in a sandbox or approved object.
4. Update a noncritical field with approval.
5. Remove or expire the token and confirm the connector fails closed.

If a field is missing or rejected, inspect Salesforce field-level security and API names before changing the connector allowlist.