Skip to main content
Zapier and Make have no connector of their own here. Connect either one, Pipedrive, Zoho CRM or anything else missing from the connector list the same way: a webhook to send leads out, and the public leads API to bring them in.
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.

​
Is there a Zapier or Make connector?

No. Open Add integration on and the list holds ten connectors: Calendly, Cal.com, Brevo, HubSpot, HeyReach, Salesforce, Odoo, Kommo, Slack and Webhook. Zapier, Make, Pipedrive, Zoho CRM and n8n are not on it, and nothing adds an eleventh option: the ten are a fixed list in the product, not a per-workspace one. Webhook stands in for all of them. Point it at a Zap’s catch hook or a Make scenario’s webhook trigger and it gets a card on that page like any other connector, carrying the name you gave it, or the endpoint’s own domain when you left the name blank.

​
Send leads out to Zapier, Make or anywhere else

Two ways, and you do not need to set up both.
  • The Webhook connector: a saved endpoint with its own authentication and field mapping, added once from Add integration. Push to CRM on a lead’s own page can send it there, and so can turning on Auto-push analyzed leads on the connector’s own card.
  • The Send Webhook block: a step on a workflow canvas. Its Endpoint control offers Custom URL, a one-off address typed straight into the block, or Saved connector, the same webhook connector, with any fields you add on the block merged on top of its own mapping.
A webhook is not treated as the lead’s CRM of record. Unlike HubSpot, HeyReach, Salesforce, Odoo and Kommo, it never claims the lead, so connecting a real CRM afterwards still pushes, and it accepts a lead with no email address, where a record-creating CRM refuses one. Slack behaves the same way for the same reason. If your Zap or scenario answers with a JSON body carrying the id of the record it created, we store that id on the lead, and the button on the lead reads Synced to CRM instead of Push to CRM. Two things stop that: switching off Store the ID returned by the endpoint in the connect dialog, and a record-creating CRM that already owns the lead, whose id we never overwrite. Connect a webhook sets up the connector step by step. Webhook testing, delivery rules and record IDs covers what a test result and a 2xx status actually prove.

​
Bring leads in from Zapier, Make or anywhere else

The other direction is not a webhook at all. It is the public leads API, /api/v1, authenticated by a workspace API key instead of a signed-in session. Create one from by choosing Create key: its Name field suggests naming it after the system that will use it, with the placeholder text “e.g. Website form, Zapier, Internal CRM”. Under Permissions, leads:write is already ticked, and that is the one the intake endpoint needs. Then have your Zap or scenario call POST /api/v1/leads whenever it has a new lead to send. API overview covers authentication, scopes and rate limits in full.
API & Integrations is a stricter bar than Apps & CRM: Admin, Member and Viewer can all open Apps & CRM, but only Admin can open the API tab. If you can connect a webhook and still cannot reach the key screen, that is why.

​
What about Pipedrive, Zoho CRM or another CRM that isn’t listed?

The same webhook path. Neither has a connector of its own, so each connects the way any tool without one does: a Webhook pointed at whatever endpoint that CRM, or a Zap or scenario standing in front of it, accepts leads on. CRM and integration blocks covers pushing a lead there automatically from inside a workflow.

Connect a webhook

Set up the connector step by step: the endpoint, the authentication, the field mapping, tested before you save.

Webhook testing, delivery rules and record IDs

Read a test result, understand why a 2xx isn’t proof, and fix the endpoints we refuse to call.

API overview

Authenticate with a key, scope it, and see what actually counts as the public contract.

CRM and integration blocks

Push a lead to your CRM, post to Slack or call any endpoint, as a step inside a flow.