Skip to content

Connect Zapier, Make or n8n

Start an automation when something happens in HeyLeads, and add leads to HeyLeads from an automation.

4 min read · Updated November 18, 2026

HeyLeads doesn't have its own app inside these tools yet. You use their built-in webhook and HTTP steps instead, which takes a few more clicks but works the same way. There are two directions, and you can use either or both.

  • HeyLeads to your tool: a reply, an accepted request or a finished campaign starts your Zap, scenario or workflow.
  • Your tool to HeyLeads: an automation adds leads to a HeyLeads list.
Settings, Integrations, Zapier. Make and n8n have the same layout.

#A. Send HeyLeads events to Zapier

  1. In Zapier, choose Create, then Zap. For the trigger choose Webhooks by Zapier, event Catch Hook

  2. Copy the Custom Webhook URL

    It starts with https://hooks.zapier.com/hooks/catch/.

  3. In HeyLeads, open Settings, Integrations, Zapier and paste it into Zapier URL

  4. Under Send me, pick events

    It starts at Positive replies only. Other quick choices: Replies, Replies and accepted requests, Everything.

  5. Choose Connect Zapier

    A signing secret appears once. Zapier's Catch Hook can't check signatures, so you can close it.

  6. Send a test and add your next step in Zapier

    In Zapier choose Test trigger, then in HeyLeads Send test. A sample with the event webhook.test should appear.

#A. Send HeyLeads events to Make

  1. In Make, create a scenario and add the Webhooks module, then Custom webhook, Add, and name it HeyLeads

    Leave the optional API key authentication and IP restrictions off.

  2. Copy the address Make shows

    It starts with https://hook. and ends in make.com.

  3. In HeyLeads, open Settings, Integrations, Make, paste it into Make URL, pick events and choose Connect Make

  4. In Make choose Run once, then Send test in HeyLeads

#A. Send HeyLeads events to n8n

  1. In n8n, start a workflow with a Webhook node

    Set HTTP Method to POST, replace the path with a long random one, such as heyleads-8f3k29xq7d, and set Respond to Immediately. The path is what keeps strangers out.

  2. Copy the Production URL, not the Test URL

  3. In HeyLeads, open Settings, Integrations, n8n, paste it into n8n URL, pick events and choose Connect n8n

  4. In n8n, activate the workflow so the Production URL starts listening

A self-hosted n8n must be reachable from the internet over https. Addresses on a private network, such as localhost, are refused. The n8n page also has a ready workflow you can paste into an empty canvas. It tags every positive reply replied-positive.

#B. Add leads to HeyLeads from your tool

  1. On the same HeyLeads page, under The other direction: add leads, choose Create a key for this and copy it

    It's shown once. Use a separate key per tool so you can revoke it alone.

  2. In your tool, add a step that makes a web request

    Zapier: Webhooks by Zapier, Custom Request. Make: HTTP, Make a request. n8n: HTTP Request.

  3. Set the method to POST and the URL to https://YOUR_HEYLEADS_ADDRESS/api/v1/lists/LIST_ID/leads

    Your address and the list's ID are shown on the page.

  4. Add the headers Authorization: Bearer YOUR_API_KEY and Content-Type: application/json

  5. Send the lead as JSON in the body

Request body
{ "rows": [ { "fullName": "Ada Lovelace", "linkedinUrl": "https://www.linkedin.com/in/ada-lovelace", "company": "Analytical Engines", "email": "ada@example.com" } ] }

People already in HeyLeads (matched by LinkedIn link) are skipped, not moved or duplicated. Adding someone to a list doesn't contact them.

#If something goes wrong

What you seeWhat it means
Webhook URLs must start with https://You pasted an address starting with http. Copy it again.
The tool finds no sampleStart the tool's test first so it's waiting, then press Send test in HeyLeads.
401 unauthenticatedThe key is missing, mistyped or revoked. The header must read Bearer, a space, then the key.
403 forbiddenThe key's access level is too low. Use Member or higher.
422 invalidThe JSON is broken, or has a field next to rows that the call doesn't know.
429 rate_limitedToo many calls this minute. Wait for Retry-After, or send up to 5,000 rows in one call.
The tile says PausedThe endpoint was switched off, or switched off after 20 failed deliveries in a row. Fix the cause and flip it on.
Was this article helpful?