Skip to main content
Authorize a Salesforce org, production or sandbox, so you can push leads there as Lead records with their email history attached as tasks.
Where
Integrations→Integrations→Apps & CRM
Your role needs
Read access to Apps & CRM read-integrations. Admin, Member and Viewer have it by default.
To create or change
create-integrations to add one, update-integrations to change one, on top of the permission above.
If you cannot find this in your sidebar, your workspace may have a custom menu configuration. Contact support and we will check it for you.

​
Before you begin

  • A Salesforce login for the org you want to connect, production or sandbox.
You are never asked for credentials of your own. The connect dialog collects exactly one thing, the environment. There is no API key field, no client ID field, and nothing to copy out of Salesforce beforehand.

​
Steps

1

Open the Salesforce connect dialog

Go to , choose Add integration, then choose Salesforce from the list. The dialog opens with a short description of what connecting shares, an environment choice, and a Connect Salesforce button.
2

Choose an environment and connect

Production is selected when the dialog opens, and it connects a live org through login.salesforce.com. Sandbox connects a sandbox org through test.salesforce.com instead. Nothing on the card afterwards records which one you chose, so this dialog is the one place to get it right.Choose Connect Salesforce. The browser leaves this screen for Salesforce’s own sign-in page.
3

Sign in and authorize on Salesforce

This page is Salesforce’s own, not ours: whatever your org’s sign-in and consent screens look like is what you see. Approve access and Salesforce sends you back. We never see your Salesforce password. What we keep is an access token, plus a refresh token we exchange for a new one whenever a push comes back unauthorized, so you are not asked to sign in again.
4

Land back, connected

You come back to , the settings tab, even though you started from the sidebar. It is the same screen with the same cards, and a Salesforce card now carries a Connected chip, with the name and email of the Salesforce user you signed in as underneath. The same card is on .

​
What happens next

A “Salesforce connected successfully” toast appears, and the card shows a Connected chip with the name and email of the Salesforce user you signed in as.
Connecting again as a different Salesforce org, or a different user in the same org, adds a second card rather than replacing this one. Signing in again as the same Salesforce user updates the existing connection instead. Connecting Salesforce pushes nothing on its own. A lead reaches the org only when you switch on Auto-push analyzed leads on the card and then choose Save (the switch alone changes nothing until it is saved), or choose Push to CRM on a lead’s own page, or run a workflow whose Send to CRM step points at this connector. That switch needs the update-integrations permission, separate from the one that let you connect the account: a role without it gets the card with no auto-push block on it at all. See Auto-push analyzed leads and stage filters and Push a lead to your CRM manually. Only one CRM ever owns a lead. If HubSpot, Odoo, Kommo or HeyReach has already claimed it, the automatic push skips it without telling you, and a workflow’s Send to CRM step takes its Sent branch without creating anything. A manual push from the lead’s own page is the one route that still goes through. Once a lead is pushed, Salesforce gets a Lead record carrying its name split into first and last, its most recently added email and phone number, its job title, its company’s website and industry, a Lead Source set to your workspace’s brand name, and a description built from its LinkedIn URL, its own description, its company’s description and summary, and its company’s links, leaving out whichever of those it does not have. Salesforce requires both a last name and a company on every Lead, so a one-word lead name is filed as the last name, and a lead with no company, or no name at all, is filed under the literal word “Unknown”. The same notes are then logged again as their own completed task, and every email in the lead’s thread becomes its own completed task too, skipping only warm-up traffic. Field mapping reference per CRM has the complete, field-by-field version.

​
Troubleshooting

The card says Connected and no Lead records appear. Three things stop a push, in the order worth checking. Auto-push analyzed leads is off, or it was switched on and never saved. The lead has no email address, which the automatic push skips and the manual button refuses with “Cannot push lead to CRM without an email address”. Or another record-creating CRM already claimed the lead, in which case the automatic push and a workflow’s Send to CRM step both skip it in silence. Auto-push analyzed leads and stage filters goes through every reason a lead is skipped.
You came back from Salesforce but the connection did not complete, either because the token exchange with Salesforce failed or because the browser lost the session the authorization was started in. Finish the round trip in the same browser you started it in, and in one sitting. The message reads the same whatever the cause, so there is nothing more specific to read: open Add integration and try again.
Salesforce requires both a last name and a company on a Lead record, and not every lead has both. A one-word lead name becomes the last name; a lead with no company name, or no name at all, is filed under the literal word “Unknown”. Field mapping reference per CRM covers every fallback like this one, across every connector.

Field mapping reference per CRM

What object each connector creates, which lead fields land where, and what happens to your email history.

Auto-push analyzed leads and stage filters

What triggers an automatic push, which stages it fires on, and every reason a lead is silently skipped.

Push a lead to your CRM manually

Send one lead to a connected CRM from the lead page, and read the Synced to CRM badge it leaves behind.