Salesforce integration · CRM
Send chat leads straight to Salesforce.
SuperBot connects to Salesforce over OAuth: you sign in to Salesforce and approve access, with no key to paste. Each event SuperBot sends creates a Salesforce Lead with the visitor's name, email, phone, company, and message, and LeadSource set to “SuperBot”.
- OAuth sign-in
- SuperBot → Salesforce (Lead records, write)
- Free, Starter & Pro
How the Salesforce integration works
Salesforce is the one CRM connector that uses OAuth. After you approve access, SuperBot stores an encrypted access token and refresh token for your Salesforce instance. Access tokens expire, so SuperBot refreshes them automatically when Salesforce says one is out of date.
A Salesforce connection receives all four events. Each delivery creates a new Lead record; SuperBot does not search for or merge existing Leads, so use Salesforce's own duplicate and matching rules if you need de-duplication.
- New lead captured
- Form submitted
- New conversation started
- Conversation escalated to a human
A Salesforce connection receives all four events.
What gets sent
| From SuperBot | In Salesforce |
|---|---|
| Name (first word) | FirstName |
| Name (rest), or the email's local part | LastName (required by Salesforce) |
| Company, or “Unknown” | Company (required by Salesforce) |
| Phone | Phone |
| Message | Description |
| — | LeadSource = “SuperBot” |
Salesforce requires LastName and Company on every Lead, so SuperBot fills sensible fallbacks rather than failing the delivery.
Connect Salesforce to SuperBot
- Open Dashboard → Integrations in SuperBot and choose Salesforce under “Available connectors”.
- Select “Connect Salesforce”. You are sent to the Salesforce sign-in page.
- Sign in with a Salesforce user that can create Leads, review the requested access (API access and a refresh token for offline use), and approve.
- Salesforce returns you to SuperBot, and the connection appears under “Connected” as Salesforce.
- Use “Send test” to create a sample Lead (Test Lead at Acme Co.), confirm it in Salesforce, then delete it.
Don't have a workspace yet? Sign up free — no card needed — then open Dashboard → Integrations.
Permissions and privacy
- OAuth scopes requested: api, refresh_token, and offline_access. SuperBot uses them only to create Lead records and to check the connection.
- Tokens are encrypted before storage and never reach the browser.
- Transcripts are not synced; the latest message is sent as the Lead description.
- Disconnect removes the stored tokens. You can also revoke the connected app from your Salesforce user settings.
What teams use Salesforce with SuperBot for
- Route inbound chat to sales
Every chat lead lands as a Salesforce Lead tagged with LeadSource SuperBot, so assignment rules and reports pick it up.
- Report on chat as a channel
Filter Leads by LeadSource to see how many came from the website assistant compared with your other channels.
- Escalations your reps can see
When a visitor asks for a human, the escalation becomes a Lead too, with their message in the description.
FAQ
Salesforce integration questions, answered.
Ready to try it? Start free or compare plans. Every integration is on every plan.
Do I need to paste a Salesforce API key?
No. Salesforce connects over OAuth. You sign in to Salesforce, approve access, and SuperBot stores the resulting tokens encrypted.
Does SuperBot update existing Salesforce Leads or Contacts?
No. It creates a new Lead for each event it sends. Use Salesforce duplicate rules if you want matching or merging.
Which Salesforce fields does SuperBot fill?
FirstName, LastName, Company, Email, Phone, Description, and LeadSource (always “SuperBot”). LastName and Company get fallbacks because Salesforce requires them.
What happens when the access token expires?
SuperBot refreshes it with the stored refresh token and retries the request once, then saves the new token for the next delivery.
Is Salesforce an extra cost in SuperBot?
No. Every integration, Salesforce included, works on Free, Starter, and Pro.