Send chatbot leads to Salesforce
A Lead, a Contact, or any object your org creates
A lead from the chat becomes a record on the object you pick -- Lead, Contact, Account, or one of your own -- with the fields read from your org rather than from a template.
What it does
Your org's fields, not ours
The mapper reads the object's describe, so it offers the fields your admin created and the picklist values they actually allow.
Sandbox or production
A sandbox logs in at its own host. The connection asks which, because a sandbox token presented to production is refused as if it had been revoked.
Every object the user can create
Lead, Contact, Account, Opportunity and Case first, then everything else the org exposes, grouped so the picker stays usable.
How to connect it
Read the full guide- 1
Create a connected app
In Salesforce Setup, with the api and refresh_token scopes. Note the consumer key and secret.
- 2
Get a refresh token
Authorise the app once. The refresh token lasts until somebody revokes it.
- 3
Connect Salesforce
Paste the four values and say whether it is production or a sandbox.
- 4
Map the fields
Auto-map, then check it. A Lead needs a last name and a company, and both are filled in when the mapping leaves them out.
Questions people ask
Does it need an integration user?
It acts as whoever authorised the connected app. A user without Create on the object cannot create there, and the refusal names the object rather than the person.
What happens to duplicates?
Your org's duplicate rules apply as they would to any API insert. We create; Salesforce decides.
Can it update an existing record?
Not yet. This route creates. Matching an existing record means deciding which field is the identity, and that is a setting we would rather ask for than guess.
What teams use it for
Upload your documents, get answers that cite them
One knowledge base, an AI chat or an Ask AI search on any site, and every answer with the passage it came from. Free for 14 days.