Salesforce

At a glance

Availability: Experimental (how to enable).
Authentication: OAuth 2.0.
Connection: A user authorizes the connection in the provider’s consent screen.
Scopes: api, refresh_token, offline_access.

Credentials

Set these per environment. See Connect an integration. These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

Variable	Required	Description
`SALESFORCE_CLIENT_ID`	Yes	Salesforce OAuth Consumer Key (from your Connected App) Docs.
`SALESFORCE_CLIENT_SECRET`	Yes	Salesforce OAuth Consumer Secret Docs.

Setup

Create a Salesforce test org: Use a sandbox or free Developer Edition org for staging. Enable Service Cloud, Cases, and Knowledge if the demo needs support workflows.
Create a Connected App: In Salesforce Setup, create a Connected App with OAuth enabled. Add the Veryfront callback URL for the target environment.
Configure OAuth scopes: Add api, refresh_token, and offline_access scopes. Use the Web Server Flow with a client secret for Veryfront API environments.
Store Veryfront environment credentials: Set SALESFORCE_CLIENT_ID and SALESFORCE_CLIENT_SECRET for the matching Veryfront environment. Keep staging and production credentials separate.
Grant least-privilege Salesforce permissions: Assign the connected user access to Account, Contact, Case, CaseComment, Opportunity, Lead, and Knowledge objects required by the enabled tools.

Provider notes

Staging callback: https://api.veryfront.org/oauth/callback/salesforce
Production callback: https://api.veryfront.com/oauth/callback/salesforce
Write tools should be explicitly enabled for an agent or project; read tools are the default demo surface.

Provider API reference.

Project configuration

Project integration configuration is optional. When config is missing or {}, Salesforce tools keep the default compatibility behavior. New Studio saves use the object-first shape below; older allowedSObjects, allowExpertSoql, and maxQueryRows configs are still accepted during migration.

Field	Type	Default in the Studio form	Runtime effect when saved
`dataAccess.objects`	Array of Salesforce object API names	`Account`, `Contact`, `Case`, `CaseComment`, `KnowledgeArticleVersion`, plus objects required by currently selected tools	Restricts Salesforce tools to selected objects. Custom and managed-package objects such as `Customer__c` or `ns__Subscription__c` can be added by API name. Omit it or use an empty list to avoid a project-level object filter. Salesforce permissions still apply.
`capabilities.allowExpertSoql`	Boolean	`false`	Allows the raw `run_soql_query` expert path only when the tool is also explicitly enabled in the project tool list.
`capabilities.maxQueryRows`	Integer from `1` to `2000`	`100`	Rejects SOQL queries whose top-level `LIMIT` is above this value. Omit it to avoid a project-level row limit.
`mappings.customer`, `mappings.contact`, `mappings.case`, `mappings.knowledge`	Optional mapping objects	Account/contact/case/knowledge defaults	Records how this org maps Veryfront concepts to Salesforce objects, identity fields, display fields, and relationships. These fields store mapping metadata; they do not automatically rewrite individual tool queries.

Recommended Service Cloud support config:

salesforce-config.json

{
  "dataAccess": {
    "objects": [
      "Account",
      "Contact",
      "Case",
      "CaseComment",
      "KnowledgeArticleVersion"
    ]
  },
  "capabilities": {
    "allowExpertSoql": false,
    "maxQueryRows": 100
  },
  "mappings": {
    "customer": { "object": "Account", "identityFields": ["Name"], "displayField": "Name" },
    "contact": { "object": "Contact", "identityFields": ["Email", "Name", "Phone"], "displayField": "Name" },
    "case": { "object": "Case", "customerRelationship": "AccountId", "displayField": "CaseNumber" },
    "knowledge": { "object": "KnowledgeArticleVersion" }
  }
}

Enable write tools separately with the project tool allowlist. For example, select create_case, add_case_comment, or update_case only for agents that need to change Salesforce records.

Tools

Tool	Access	Description
Find Customer `salesforce__find_customer`	Read	Find customer contacts with account context for support triage. Pass a focused SOQL query when searching by email, name, phone, or account.
Search Accounts `salesforce__search_accounts`	Read	Search Salesforce accounts with business context for support or sales work
Get Account `salesforce__get_account`	Read	Get detailed information about a specific account
Search Contacts `salesforce__search_contacts`	Read	Search contacts with account fields for CRM follow-up and support context
Get Contact `salesforce__get_contact`	Read	Get a Salesforce contact by ID
List Cases `salesforce__list_cases`	Read	List Service Cloud cases for a customer, account, owner, status, or queue
Get Case `salesforce__get_case`	Read	Get a Service Cloud case by ID
List Case Activity `salesforce__list_case_activity`	Read	List case comments for support handoff, timeline review, and resolution context
Search Knowledge Articles `salesforce__search_knowledge_articles`	Read	Search published Salesforce Knowledge articles that can help answer or deflect a support case
List Opportunities `salesforce__list_opportunities`	Read	List Sales Cloud opportunities for account planning and customer context
Create Lead `salesforce__create_lead`	Write	Create a new lead in Salesforce CRM
Create Case `salesforce__create_case`	Write	Create a Service Cloud case for customer support
Add Case Comment `salesforce__add_case_comment`	Write	Add a support note or customer-visible comment to a Service Cloud case
Update Case `salesforce__update_case`	Write	Update case details, classification, ownership, or resolution fields on a Service Cloud case
Describe Object `salesforce__describe_object`	Read	Get metadata and field definitions for a Salesforce object
Run SOQL Query `salesforce__run_soql_query`	Read	Run a read-only SOQL query for expert inspection when curated tools are not enough

Verify the connection

Call a read tool such as salesforce__find_customer with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.

Salesforce tool policy and mappings: How object access, tool selection, and mapping metadata apply to Salesforce calls.

Get started

APIs

REST API

GraphQL API

MCP API

At a glance

Credentials

Setup

Provider notes

Project configuration

Tools

Verify the connection

​At a glance

​Credentials

​Setup

​Provider notes

​Project configuration

​Tools

​Verify the connection

​Related

At a glance

Credentials

Setup

Provider notes

Project configuration

Tools

Verify the connection

Related