Skip to main content

At a glance

  • Availability: Experimental (how to enable).
  • Auth: 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. With a managed OAuth app, Connect works without these variables; set them to use your own OAuth app instead.

Setup

  1. 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.
  2. Create a Connected App: In Salesforce Setup, create a Connected App with OAuth enabled. Add the Veryfront callback URL for the target environment.
  3. Configure OAuth scopes: Add api, refresh_token, and offline_access scopes. Use the Web Server Flow with a client secret for Veryfront API environments.
  4. Store Veryfront environment credentials: Set SALESFORCE_CLIENT_ID and SALESFORCE_CLIENT_SECRET for the matching Veryfront environment. Keep staging and production credentials separate.
  5. 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 API reference: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_rest.htm

Tools

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. Recommended Service Cloud support config:
salesforce-config.json
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.

Example prompts

  • Find the customer in Salesforce, summarize their open cases, and suggest the next support action.
  • Create a Salesforce Service Cloud case with the customer, subject, priority, and issue summary I provide.
  • Search Salesforce Knowledge for articles that answer this customer support issue.
  • Summarize Salesforce opportunities for this account and highlight any renewal or expansion context relevant to support.