Integrations
Salesforce
Connect Salesforce, obtain the required access and configure permitted actions.
The API adapter is implemented. Validate your own account and authorized actions before routing production calls.
Before you start
Connect the account belonging to this business and workspace. Vendor subscriptions, API limits and role permissions still apply.
API: Salesforce REST API, sObjects, Describe and Composite API
Authentication: Customer OAuth through the existing Salesforce connector (preferred); short-lived Bearer access token for diagnostics
Get access and connect
- Use an API-enabled Salesforce organization or sandbox. Ask its administrator for an integration user with the intended object and field permissions.
- Open Integrations → Salesforce and select Connect. Authorize the integration user. Your administrator may need to approve Verbatik’s External Client App.
- Link that connected account when configuring native Salesforce actions. Set the exact instance origin, such as https://your-company.my.salesforce.com.
- Run Test connection, then Describe object to obtain your organization’s field names and picklist values. Add selected actions to the agent and publish.
- For ongoing use, keep the OAuth connection linked so its token can be renewed. A manually supplied access token works only until Salesforce expires or revokes it.
Account requirements
- The user needs API Enabled plus read/create/edit privileges and field access for Contact, Account, Lead, Opportunity and Task as used by the selected actions.
- Enhanced notes require ContentNote and ContentDocumentLink access and the Notes feature enabled for the organization. Required custom fields, validation rules and restricted picklists can reject otherwise valid generic record writes.
- Production API access depends on the Salesforce edition and account configuration; a sandbox or Developer Edition should be used for first writes.
- There is no static Salesforce API key. Access-token-only mode does not automatically renew; link the existing OAuth connector for ongoing operation.
Permissions
apirefresh_token / offline_access
Grant the subset needed for the actions you enable. API scopes do not override the connected user’s record permissions or vendor validation rules.
Connection fields
accessToken— Salesforce OAuth access token (required). Secret fields are saved as workspace credentials.instanceUrl— Salesforce instance URL (required).
Available actions
test_connection— Read · available for after-call automation. Read account or schema metadata to verify credentials without creating records.find_contact— Read · available for after-call automation. Find Salesforce contacts by exact email. The query is built and escaped by Verbatik.get_record— Read · available for after-call automation. Read a contact, account, lead, opportunity or task by ID.create_contact— Write · available for after-call automation. Create a Salesforce contact using a known account ID when available.create_record— Write · available for after-call automation. Create a Contact, Account, Lead, Opportunity or Task with Salesforce API field names, including organization-required fields.update_record— Write · available for after-call automation. Update fields on a known Salesforce record, including opportunity StageName.describe_object— Read · available for after-call automation. Read schema, required fields and picklist values before creating CRM records.create_task— Write · available for after-call automation. Create a follow-up task linked to a known contact or lead.log_call— Write · available for after-call automation. Create a completed Salesforce Task with call fields. Does not place a phone call.add_note— Write · available for after-call automation. Create an enhanced note and link it to a CRM record atomically. Both writes must succeed.
Verify before going live
Run Test connection and one read action against a known permitted record. Then test each intended write in an authorized sandbox. Check the provider’s own record and the Verbatik receipt. Publish the agent after assigning its tools. If a write has an unknown outcome, reconcile it with the vendor before trying again.