Before you start
- A paid Zapier plan. Zapier's help lists Webhooks by Zapier on Professional, Team and Enterprise, not Free. Make's free plan does the same job; our Make guide shows how.
- 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 Zapier, create a Zap. For the trigger, choose Webhooks by Zapier, set the event to Catch Hook and click Continue.
- On the Test tab, click Copy to copy the webhook URL. It starts with https://hooks.zapier.com/hooks/catch/.
- In your dashboard, open Integrations, find "Zapier, Make and CRMs" and paste the address in. Save it, then press "Send a test lead".
- Back in Zapier, click Test trigger. You should see a request with type "test" and a lead named "Test lead". If it's still empty, press "Send a test lead" again, then Test trigger.
- Add an action for the app the lead should go to, and map its fields: name to lead name, phone to lead phone, email to lead email, and the service type, area and preferred time into a notes field.
- Switch the Zap on, and check it shows as on in your list of Zaps.
- 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 Zapier Help: Trigger Zaps from webhooks
Good to know
- Zapier flattens nested fields, so lead.name arrives in your Zap as lead__name.
- Check the Zap is on. Zapier's help says a request to a Zap that's off or deleted can still be answered as received for several hours, so Integrations can show a lead as accepted while the Zap did nothing with it.
- Catch Hook passes the body only. If your developer wants to check our signature header, use Catch Raw Hook instead, which keeps the headers, and check it in a Code step.
- 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 Zapier webhook free?
No. Zapier's help lists Webhooks by Zapier on its Professional, Team and Enterprise plans and not on Free. Make's free plan includes webhooks, and the Make guide does the same job with it.
Where do I find the Zapier webhook URL?
In the Zap's trigger, after you choose Webhooks by Zapier and Catch Hook and click Continue: it's on the Test tab, with a Copy button. Each Zap has its own address.
Why isn't my Zapier webhook working?
Usually the Zap isn't published, or a filter is set to keep only type lead.created, which hides the test lead. Check the Zap is on, send a test lead, and look at the Zap's run history. If Integrations shows a lead as not accepted, it names the reason and tries again on its own.