The Salesforce step turns a conversation into a Lead or a Contact in your Salesforce org, with the visitor's answers in the standard fields and any custom fields you add, the moment the chat reaches it.
Build on the Free plan. The Salesforce step runs on Pro ($39/month) and above.
Sales teams on Salesforce want chat leads where every other lead goes: in Salesforce, assigned and visible in their reports. The Salesforce step writes the record directly, so your lead assignment rules, routing and dashboards treat chat leads like any other source.
It is deliberately focused. The step creates one record per run, either a Lead or a Contact, from the standard fields Salesforce expects plus any custom fields you name. Everything else, such as assignment and follow-up tasks, stays in Salesforce where your admins already manage it.
Map first name, last name, email, phone and company to chat variables and a Lead is created in your org. This is the usual choice for new prospects from your website.
Choose Create contact when the visitor is someone you already do business with, for example in a partner or customer support flow, and the same fields create a Contact instead.
Under More fields, add any field by its API name, such as Lead_Source_Detail__c or Budget__c, and the value or variable to put in it. Names are checked against Salesforce's field-name rules before the request is sent.
Salesforce requires a last name, and a company on Leads. If the visitor did not give one, the step sends Unknown so the record is still created and your team can fill it in.
Tick Sandbox org when you connect to test the flow against a sandbox first, then connect your production org for the live bot.
Name a variable under Save result and the new record's ID is stored, ready to pass to a later step or show to your team in an alert.
| Field | What it does |
|---|---|
| Salesforce account | The connected org the record is created in. Connect production, or tick Sandbox org for a sandbox. |
| Operation | Create lead or Create contact. |
| First name, Last name | Usually ${name} and a last-name variable. Last name falls back to Unknown if empty. |
| Email, Phone | The visitor's contact details from the chat. |
| Company | Required on Leads by Salesforce; falls back to Unknown if empty. |
| More fields | Extra fields by API name, standard or custom (custom names end in __c). |
| Save result | Optional variable that stores the created record's ID. |
About ten minutes. You need a Pro or higher Conferbot workspace and a Salesforce user allowed to authorise connected apps and create Leads or Contacts.
Ask for name, email, company and phone, and anything your custom fields need, such as budget or product interest. Save each to a variable.
Drag the Salesforce step into the flow and choose Create lead or Create contact.
Choose Connect, tick Sandbox org if you are testing, and approve access on Salesforce's login page. The org appears in the account menu for every bot in the workspace.
Fill First name, Last name, Email, Phone and Company with variables. Type $ to pick them from the list.
Under More fields, enter each field's API name from Salesforce Setup, Object Manager, and the value. A fixed value such as Website chatbot in a lead-source field makes chat leads easy to report on.
Run the flow against the sandbox, check the record and your assignment rules, then switch the step to your production org and publish.
Ask the qualifying questions your SDRs would ask, then create the Lead with the answers in custom fields. Salesforce assignment rules route it to the right owner automatically.
Sales lead qualification templateB2B lead qualification template
After the Salesforce step, send the record ID and a summary to the owner with the Gmail step, so a hot lead gets a reply in minutes rather than at the next pipeline review.
In a support or partner flow, create a Contact from the visitor's details so the account team sees who reached out and why.
Create the Lead, then offer a slot with the Google Calendar step. The visitor leaves with a meeting and your rep with a Lead.
The connection asks Salesforce for API access, your identity, and a refresh token, the standard api, id and refresh_token scopes. The refresh token keeps the connection working without you signing in again each time the session ends.
Salesforce returns your org's instance address when you connect, and every request goes there rather than to a generic login server, so the step works with My Domain and sandbox orgs alike.
Records are created as the Salesforce user who approved the connection, with that user's permissions. Connecting an integration user with a dedicated profile keeps chat leads clearly separate in record history and reports.
Remove the org on the Integrations page, or revoke the connected app in Salesforce under the user's connected apps. Salesforce steps stop writing until you reconnect.
Each run creates a new Lead or Contact. The step does not search for an existing record first, so use Salesforce's duplicate rules if returning visitors should be matched.
The integration uses Salesforce's REST API, which is available on the Salesforce editions that include API access. Check your edition in Salesforce Setup if the connection is refused.
The record is created as the user who connected the org. If that user cannot edit a field, Salesforce rejects the value, so connect with a user whose profile can write every field you map.
Each run uses one API request from your org's daily allocation. See Salesforce API request limits.
If the request fails, the visitor still finishes the conversation and the result variable stays empty. Check it if you want to alert your team instead.
| What you see | Why, and the fix |
|---|---|
| "The saved account is no longer connected" | The org connection expired or was revoked in Salesforce. Reconnect from the step or the Integrations page. |
| Records show "Unknown" as the last name or company | The visitor did not answer those questions, or the variables are empty when the step runs. Ask for them before the step if they matter. |
| A custom field is ignored or rejected | The API name is wrong (custom fields end in __c) or the connected user lacks edit access to it. Copy the name from Object Manager and check field-level security. |
| Leads land with the wrong owner | Ownership comes from your Salesforce assignment rules. Check the rules for your lead-source value. |
| Testing affected live data | Connect a sandbox org with Sandbox org ticked while testing, and switch the step to production only when the flow is final. |
Yes. The Salesforce step creates a Lead, or a Contact if you choose, each time a conversation reaches it, using the visitor's answers for the fields you map.
Yes. Add any field by its API name under More fields, including custom fields ending in __c, with a fixed value or a chatbot variable.
Yes. Tick Sandbox org when connecting to sign in through test.salesforce.com, then connect your production org once the flow works.
Salesforce requires a last name, and a company on Leads. If the answer is missing, the step sends Unknown so the record is still created.
No. Each run creates a new record. Use Salesforce duplicate and matching rules if returning visitors should be merged.
Salesforce is a native integration, included on Pro and above. You can build and preview the flow on any plan.
Any edition that includes REST API access, because the integration creates records through Salesforce's API as the user who connected the org.
Yes. Set a variable under Save result and the ID of the created Lead or Contact is stored for later steps, such as an alert email to the owner.
Yes. Add a Salesforce step and a Google Sheets step one after the other. Both read the same chat variables, so one conversation creates the Lead and appends a row for teams that track chat leads outside Salesforce.
Start free with Conferbot - the free plan includes 600 conversations a month and needs no credit card, so you can build the qualification flow today. The Salesforce step switches on with Pro.
Checked against Conferbot's product and Salesforce's documentation on November 3, 2026: Salesforce REST API, Salesforce API request limits.
Explore features, connect third-party tools, and browse ready-made templates.
Deep-dive pillar guides, real use cases, and the chatbot & AI glossary.
Guides on getting chat leads to sales quickly.
