Before you start
- A Make account. The free plan includes 1,000 credits a month, according to Make's pricing page.
- The lead webhook on your plan. Open Integrations in your dashboard: if the "Zapier, Make and CRMs" card says "Not on your plan", your plan doesn't include it. The trial does.
- An account in the app the leads should go to.
Steps
- In Make, create a new scenario. Add the Webhooks app and choose the Custom webhook module.
- Click Add next to Webhook, give it a name such as "Website leads" and click Save. Leave API Key authentication empty. Copy the address Make shows.
- In your dashboard, open Integrations, find "Zapier, Make and CRMs" and paste the address in. Save it, then press "Send a test lead".
- Go back to Make and it will have learned the shape of a lead. If it's still waiting, press "Send a test lead" again.
- Add a module for the app the lead should go to, and map its fields: lead.name, lead.phone and lead.email, with lead.serviceType, lead.addressOrArea and lead.preferredTime in a notes field.
- Save the scenario and switch it on. While it's off, Make holds incoming leads in the webhook's queue and does nothing with them.
- Press "Send a test lead" once more and check "Test lead" on +44 7700 900000 arrives in that app, then delete it. Then leave a real inquiry on your own website and watch that arrive too.
Platform steps checked on November 13, 2026 against Make: Webhooks app documentation
Good to know
- Leave Make's API Key authentication off. It needs a header we don't send, so every lead would be refused. Every request we send is signed instead; the signing secret is under "For whoever sets it up" on the webhook page.
- Make answers "Accepted" as soon as a lead is in its queue, so Integrations counts it as delivered even if the scenario is off. Switching it on processes what's waiting.
- Make switches off a webhook that hasn't been attached to any scenario for more than 5 days. If you delete the scenario, leads start failing; make a new webhook and paste its address in.
- A webhook's queue holds a limited number of waiting leads, set by your plan. When it's full Make refuses new ones, and we try each again later.
- The test lead is marked type "test" and a real one "lead.created". That's useful for keeping tests out of a live CRM, but if you add that filter before testing, the test button will look broken. Test first, filter afterwards.
- Each lead also says where it came from. source.page is the page it was asked from, source.referrer the site that sent the visitor and source.utm.campaign the campaign tag on your link. lead.qualifying holds the answers to your own questions, and lead.serviceArea says inside, outside or unknown if you've listed the places you serve. Map any of them to a custom field.
- A lead that's refused is retried after 5, 10, 20, 40 and 80 minutes. Fix the problem within about two and a half hours and the lead still arrives on its own.
- Every retry of one lead carries the same id, so a repeat is safe to ignore.
- Leads you mark as junk are never sent, so your CRM stays clean.
Questions
Is the Make webhook free?
Yes, on Make's free plan, which comes with 1,000 credits a month. Zapier's equivalent, Webhooks by Zapier, needs a paid plan; the Zapier guide covers it if you already pay for Zapier.
Why isn't my Make webhook working?
Most often the scenario is switched off, so leads sit in the queue; switch it on. Next most often, API Key authentication was turned on, which we can't send. If the webhook was left without a scenario for more than 5 days, Make switches it off: make a new one and paste its address into Integrations.
Can one Make scenario send each lead to two places?
Yes. An assistant sends to one webhook address, but a scenario can write to several apps, such as your CRM and a Google Sheet. Every lead still reaches you by email alert either way.