By Gatedleads team · October 3, 2026

How to Set Up a Zapier Integration With Your Lead Magnet Page

A lead magnet is only useful if the lead ends up somewhere you will act on it: your email tool, a CRM, a spreadsheet, a Slack channel. Zapier is the common way to connect those. This guide shows how to wire a Gatedleads page to Zapier so that every new lead is sent on automatically, the moment they submit the form.

Zapier is a genuine integration here, not a workaround. Gatedleads sends each lead to a webhook URL, and Zapier's Catch Hook trigger receives it. From there you build whatever Zap you like.

One requirement first: Zapier and webhooks are a Pro feature ($29 per month). On the Free plan the webhook field is locked, and the server refuses to save a webhook URL for a Free account. If you are on Free, leads still land in your dashboard and you can export a CSV at any time. More on that near the end.

How the webhook works

Before setting anything up, it helps to know exactly what happens, because it explains the testing and troubleshooting steps later.

  • You set one webhook URL per page.
  • When someone submits the form on that page, Gatedleads saves the lead, then sends an HTTP POST to your URL with a JSON body.
  • If the page uses confirmation emails (double opt-in), the webhook fires when the visitor confirms their address, not when they first submit.
  • The request has a short timeout of about five seconds, and it is sent once. It does not retry if your endpoint is down or slow.
  • The request carries no signature or custom headers, which is why any generic inbound webhook can read it.
  • The webhook only fires while the account is on Pro.

The JSON body contains these fields:

  • event: always lead.created
  • pageId and slug: which page the lead came from
  • email, name, phone, company: what the visitor entered. Fields you did not collect are empty.
  • source: where the visitor came from, based on the referring page
  • createdAt: a timestamp

One detail to plan around: the UTM source, medium and campaign are stored with each lead and appear in your dashboard and CSV export, but they are not part of the webhook body today. If you rely on UTM data inside Zapier, take that into account. Our post on UTM links for lead magnets covers using them in the dashboard.

Step 1: Create the Zap and copy the webhook URL

  1. In Zapier, create a new Zap.
  2. For the trigger, choose Webhooks by Zapier.
  3. Choose the Catch Hook event.
  4. Zapier shows you a custom webhook URL. Copy it. It looks like https://hooks.zapier.com/hooks/catch/ followed by a long ID.

Leave the Zap open on the test step. Zapier will wait for a sample request, and the next steps send it one.

Step 2: Paste the URL into your page

There are two places to do this in Gatedleads, and either works:

  • From the page editor: open your page, go to the Settings tab, find the Zapier or webhook URL field, and paste the address.
  • From Integrations: open Integrations in the app and use Connect, which takes you straight to that field for the page you pick.

Save the page. Remember it is per page, so if you have five pages, each one needs its own URL. You can paste the same Zapier URL into several pages if you want all their leads to flow into one Zap, and use the slug field to tell them apart.

Step 3: Send a test lead

Zapier needs one real request to learn the shape of the data. Open your published page in a private browser window and submit the form with an address you control, such as a personal inbox. This creates a real lead in your account, so delete it from your dashboard afterwards if you do not want it counted.

Go back to Zapier and click the test button. It should find the request and show the fields listed above. If it does, pick the test record and continue.

Step 4: Add the action

Now decide what should happen to each lead. A few common patterns:

  • Add a row to a spreadsheet. Map email, name and createdAt to columns, and add slug so you know which page each lead came from. We have a full walkthrough in sending landing page leads to Google Sheets.
  • Add a subscriber to your email tool. Map email and name, and tag the contact with the page slug so you can send the right follow-up.
  • Create a CRM contact. Map the fields and, if you use the company field, set it on the account.
  • Post a message in Slack or send yourself an email. Useful when each lead is worth a personal follow-up.

If you want to know what to send new subscribers, see what to send a new lead in the first 7 days.

Turn the Zap on once the action tests correctly.

Step 5: Check the whole path

Submit another test lead and watch it travel: form, dashboard, Zap run, destination. Do this once on the live page before you start promoting it. It takes two minutes and catches the usual mistakes, such as a field mapped to the wrong column.

Troubleshooting

The lead is in my dashboard but not in Zapier. Check the plan first. If the account is not on Pro, the webhook does not fire. Then check that the URL is saved on the right page, and that the Zap is switched on. Because the request is sent once with a short timeout, a Zapier outage at that moment means that lead will not be delivered. Your dashboard and CSV export still have it.

Zapier says it never received a request. You probably tested before saving the page, or you pasted the URL on a different page than the one you submitted. Re-check the URL and submit another test.

Leads from before I connected Zapier did not arrive. The webhook sends new leads only. Export a CSV from the dashboard and import it into your destination for the earlier ones.

I get leads twice. Check whether you pasted the same URL on two pages, or built two Zaps from the same hook. Also check whether you are testing with double opt-in on, where the lead is created at confirmation.

Fields are empty. You only receive what the form collected. If you did not switch on the phone or company field, those arrive empty.

When you do not need Zapier

If you only need leads in one place and a daily or weekly look is enough, the CSV export from the dashboard works on every plan, including Free. Some people also prefer to send leads straight into a CRM without a middle layer. We cover options in sending leads to a CRM without Zapier, and in replacing the Zapier, Sheets and PDF stack for people who want fewer moving parts.

Zapier earns its place when you want an instant, automated hand-off: the lead is in your email tool before they have closed the tab.

FAQ

Do I need the Pro plan to use Zapier with Gatedleads?

Yes. Zapier and outbound webhooks are a Pro feature. Free accounts cannot save a webhook URL, and the webhook does not fire unless the account is on Pro. CSV export is available on every plan.

What does Gatedleads send to Zapier?

A JSON body with the event name, page ID, page slug, email, name, phone, company, source and a timestamp. Fields you did not collect are sent empty. UTM values are stored with the lead in your dashboard and export but are not in the webhook body.

Does the webhook retry if it fails?

No. It is sent once with a short timeout. If your endpoint is down at that moment, that lead is not re-sent, though it is still saved in your dashboard and appears in the CSV export.

Can I use Make or my own server instead of Zapier?

Yes. The webhook is a plain JSON POST, so any tool with a generic inbound webhook can receive it, including Make or your own endpoint.

Can I send different pages to different Zaps?

Yes. The webhook URL is set per page, so each page can point at its own Zap, or several pages can share one and be told apart by the slug field.

Ready to connect your first page? Sign up for Gatedleads, build the page, and add Zapier when you move to Pro.