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
- 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.
- 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.
Tools
| Tool | Access | Description |
|---|---|---|
| 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 | Read | Search Salesforce accounts with business context for support or sales work |
| Get Account | Read | Get detailed information about a specific account |
| Search Contacts | Read | Search contacts with account fields for CRM follow-up and support context |
| Get Contact | Read | Get a Salesforce contact by ID |
| List Cases | Read | List Service Cloud cases for a customer, account, owner, status, or queue |
| Get Case | Read | Get a Service Cloud case by ID |
| List Case Activity | Read | List case comments for support handoff, timeline review, and resolution context |
| Search Knowledge Articles | Read | Search published Salesforce Knowledge articles that can help answer or deflect a support case |
| List Opportunities | Read | List Sales Cloud opportunities for account planning and customer context |
| Create Lead | Write | Create a new lead in Salesforce CRM |
| Create Case | Write | Create a Service Cloud case for customer support |
| Add Case Comment | Write | Add a support note or customer-visible comment to a Service Cloud case |
| Update Case | Write | Update status, priority, owner, or resolution fields on a Service Cloud case |
| Describe Object | Read | Get metadata and field definitions for a Salesforce object |
| Run SOQL Query | Read | Run a read-only SOQL query for expert inspection when curated tools are not enough |
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.
Related
- Salesforce integration architecture: How the Salesforce tools scale across different Salesforce org models.