Salesforce integration use cases
1. Knowledge Article support bot
Published Salesforce Knowledge Articles become searchable, cited answers:
- Generate an access token from a Salesforce Connected App with read access to Knowledge.
- Import via Object Type = Knowledge. See Salesforce setup.
- Bot answers from Articles, citing the source record.
- Article suggestions to agents during ticket review, if you also index into a Help Desk workspace.
Useful when your support content already lives in Salesforce Knowledge instead of a separate docs tool.
2. Case-history troubleshooting reference
Past Case descriptions and resolutions are a record of problems already solved:
- Import via Object Type = Case. Pulls the most recently modified Cases first, up to your Max Records setting.
- Bot matches new questions against past Case descriptions the same way it matches any other indexed content.
- Useful for recurring issues — "has this error happened before?" style questions.
This is a static snapshot, not a live per-case lookup: re-run the import to refresh it with newer Cases.
What this integration does not do (yet)
To set expectations correctly:
- No lead or contact creation. The
collect_leadskill captures leads inside AskVault; it isn't wired to create Salesforce Leads or Contacts. - No live record lookups. The bot can't look up a specific visitor's Account, Opportunity, or open Case at chat time — only the Knowledge Articles and Cases you've imported as static documents.
- No outbound webhooks from Salesforce. AskVault doesn't listen for Salesforce Outbound Messages or platform events.
- No custom-object field mapping. Object types beyond Knowledge and Case can technically be queried, but only their
IdandNamefields come through — there's no UI for mapping additional fields.
If your use case depends on any of these, the custom_webhook skill is the way to bridge to your own Salesforce-connected backend today.
Setup
About 10 minutes:
- Create a Salesforce Connected App (or another way to mint an API access token) with read access to the objects you want to import.
- Open Knowledge > Add Source > Salesforce in AskVault. See Salesforce setup.
- Enter your instance URL and access token.
- Choose Object Type (Knowledge or Case) and Max Records (1–500).
- Click Import.
Plan considerations
- Free, Starter, Growth, Business. No Salesforce integration.
- Enterprise. Full read-only Knowledge Article and Case import. Enterprise
Privacy
What AskVault reads from Salesforce:
- Knowledge Articles — title, summary, article body.
- Cases — case number, subject, description.
What AskVault sends to Salesforce: nothing. The integration only issues read (SELECT) queries.
Limits
- Records per import. 1–500, set via Max Records.
- Object types. Knowledge and Case are fully supported; other object names return only
IdandName. - Salesforce API calls. Governed by your org's Salesforce edition and rate limits.
Common pitfalls
API limit hit. Salesforce's daily API limit for your org/edition. Audit usage or upgrade your Salesforce edition if needed.
Knowledge Articles missing. Your access token's user doesn't have read access to Knowledge, or the articles aren't published (PublishStatus = Online).
Import returns nothing. Your access token doesn't have read access to the object type you selected, or the matching records are too short to index.
FAQ
Does this work with Salesforce Service Cloud?
Yes — Case import reads Service Cloud Case records.
Can I sync Opportunities or Leads from chat into Salesforce?
Not today. This integration is read-only in the Salesforce direction; nothing AskVault captures gets written back. For that, bridge through the custom_webhook skill to your own Salesforce-connected backend.
Is there a live per-visitor lookup, like "what's my case status"?
Not yet. The bot answers from the Knowledge Articles and Cases you've imported as static documents, not from a live query against a specific visitor's records.
Related guides
- Salesforce integration setup
- Collect lead skill
- Custom webhook skill
- Identity verification with HMAC