Skip to main content
By the end of this page you’ve sent one lead to a connected CRM, Slack channel or webhook straight from its own page, without waiting for auto-push or a workflow to reach it.
Where
Leads→Prospects
Your role needs
Read access to Prospects read-leads. Admin, Member and Viewer have it by default.
To create or change
create-leads to add one, update-leads 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 CRM, Slack channel or webhook connected on . Connectors belong to the workspace, not to a lead, so connecting one covers every lead in it.
  • The update-leads permission. Without it the control is never drawn: it goes missing from the lead’s action toolbar rather than showing greyed out.
  • An email address on the lead, if you’re pushing to HubSpot, Salesforce, Odoo, Kommo or HeyReach. These create a contact record and need one to create it from. Slack and a webhook don’t: they deliver a notification instead of a record, so a name, a phone number or a LinkedIn link is enough.

​
Steps

1

Open the lead

Everything in this guide lives on the lead’s own page, in the action toolbar across the top, just before the assignee picker.
2

Click Push to CRM

The button reads Push to CRM on a lead with no record yet, or Synced to CRM once one exists. Either way, clicking it opens a dropdown.If nothing is connected yet, the dropdown opens straight on No CRM Connected with Connect a CRM to start pushing leads underneath, and a footer link, Add CRM Integration, that takes you to the Apps & CRM page.
3

Pick a connector

The dropdown is headed Select CRM to push, or Push to another CRM on a lead that already carries a record. Under it sit only the connectors that can receive a lead: HubSpot, Salesforce, Odoo, Kommo, HeyReach, Slack and a webhook. Calendar and booking connectors are not listed.Each row is headed by the service, HubSpot or Slack, with the name of your connection to it underneath. A webhook is the exception, because it has no brand of its own: it is headed by the name you gave it when you connected it, or, if you left that blank, by the host of its endpoint, which is what it was saved under. Its icon is the favicon of the service behind that endpoint. A connector that already holds this lead shows a green tick, and its second line becomes the date it last synced.Pick any row, including one already showing a green tick, to push again.

​
What happens next

A snackbar confirms it and names the connector you picked: “Lead successfully pushed to HubSpot”, or “Lead re-synced to HubSpot” if you picked the connector already shown as synced. The lead’s page then reloads itself, so the header comes back carrying whatever the push changed.
The button reads Synced to CRM once the lead carries a record ID, and hovering it opens a tooltip naming the connector that left the record, the date, and the ID itself. HubSpot, Salesforce, Odoo, Kommo and HeyReach always leave one. A webhook leaves one only when your endpoint answers with an id we can recognise, which webhook testing and delivery rules covers in full. Slack leaves nothing at all: it posts a message and the button stays Push to CRM. That record ID is also the claim on the lead. Auto-push and the workflow’s Send to CRM block both read it before handing a lead to a connector on their own, so a manual push to HubSpot, Salesforce, Odoo, Kommo or HeyReach stops either of them sending that lead to a second record-creating connector later. A webhook’s ID is deliberately not read as a claim, and Slack leaves none, so pushing to either still leaves a real CRM free to take the lead afterwards. The manual push itself checks none of that. It stops at whether the lead has an email address; whether a record already exists on the other side never comes up. The dropdown says as much: even on an already-synced lead its header still reads Push to another CRM, and picking the same connector again sends the identical request a second time. What that becomes on the other side depends on the CRM. Kommo is the one exception: its create endpoint applies its own duplicate control when it creates the lead, contact and company. For HubSpot, Salesforce, Odoo and HeyReach, whether a second push becomes a second contact is between you and that CRM’s own rules, not something this button checks first.

​
Troubleshooting

A catch-all failure: an expired authorization, a field the CRM rejected, or one it required and didn’t get. See Failed to push lead to CRM for the full list of causes, including the ones auto-push shares.
Nothing that can receive a lead is connected to this workspace yet. Click Add CRM Integration in the dropdown, or open the Apps & CRM overview to connect one.
Only HubSpot, Salesforce, Odoo, Kommo and HeyReach need one, because each creates a contact record from it. Use + Add Email on the lead’s Contact Information card, or push to Slack or a webhook instead, since neither needs one.

Auto-push analyzed leads and stage filters

What pushes a lead on its own, and how that differs from pushing it by hand.

Field mapping reference per CRM

What object each connector creates, and which lead fields land where.

The lead details page

Every other card and header action on a lead’s own page.