Can I use it with more than one Page or form?

Yes. One trigger subscribes to one Page and catches every form on it. A second Page means a second trigger node, which the guide shows how to add. If you only want certain forms, a filter on form ID sits right after the trigger.

Do I need to put the Meta app through App Review?

Not for your own Pages. An app left in development mode can pull leads from any Page you administer, and that is the setup the guide walks through. App Review only matters if you want the same app to serve Pages you do not own.

What happens if beehiiv rejects the call or the API key expires?

The run is marked failed in n8n and the included error workflow emails you the lead's details, so the person is never lost. Fix the credential, then re-run the failed execution from n8n's list. Meta also keeps the lead in Leads Center for 90 days as a backstop.

Does it run on Make or Zapier?

Both. The package includes a Make scenario and a Zap that follow the same steps. Facebook Lead Ads is a premium app on Zapier, so that route needs a paid Zapier plan.

Is a paid n8n plan required?

No. n8n Cloud's entry plan works, and the self-hosted community edition is free. The one hard requirement is a public HTTPS address for the webhook, which n8n Cloud provides and a self-hosted install needs a reverse proxy for.

MbhGIn build

Lead capture & routing

Meta Lead Ads form → beehiiv subscriber + Gmail alert to the owner

Every Facebook or Instagram lead lands on your list and in your inbox within a minute.

Leads from Meta instant forms sit in Meta's Leads Center until someone exports them. This workflow moves each one the moment it is submitted: the person joins your beehiiv publication with the campaign recorded as the source, and you get an email listing every answer they gave. It suits an owner or marketer who runs lead ads to feed a newsletter. Nothing changes in the ad account itself.

How it works

M
Trigger
New lead submitted on a Facebook or Instagram instant form
Meta Lead Ads
M
Step 1
Receive the lead
Meta's leadgen webhook fires on submission and the workflow fetches the answers: name, email, phone, any custom questions, plus the form, ad and campaign names.
if
Step 2
Clean the fields
Email is lower-cased and trimmed, the full name is split into first and last, the phone is put in international format, and a lead with an unusable email address stops here.
bh
Step 3
Check whether the email is already subscribed
A lookup by email against your publication decides the branch: a known subscriber skips the create step and is flagged as returning in the owner email.
bh
Step 4
Create the subscriber
New emails are added to the publication with utm_source set to meta-lead-ads, the campaign name as utm_campaign, and phone and form name written to two custom fields.
G
Step 5
Email the owner
Sent from your own Gmail, the alert carries every answer, the campaign and ad names, and a new-or-returning flag, under the subject line 'New lead: {name} via {form}'.

What changes once it runs

Each lead is a beehiiv subscriber, tagged with its campaign, within a minute of the form being submitted.
The owner's inbox gets one email per lead with every answer, so nobody logs into Ads Manager to see who came in.
Repeat submissions from the same email are recognised and flagged, not added twice.
Campaign and ad names travel with the subscriber, so beehiiv can segment by campaign.
Nothing changes in the ad account; the form, the ads and the budget are untouched.

What you get

The n8n workflow export, tested against a live Meta test lead before it ships.
Setup guide covering the Meta developer app, its permissions and the Page subscription, screen by screen.
A field-mapping sheet: each form question to its beehiiv field, ready to edit for your own form.
Recorded walkthrough of the first run using Meta's Lead Ads Testing Tool.
Make and Zapier versions of the same flow, with notes on where each differs.

Before you start

A Facebook Page running lead ads, with you as Page admin and the Page linked to a Meta Business account.
Meta developer app with the leads_retrieval permission and the Page permissions the setup guide lists.
beehiiv on a plan with API access (Scale or above at the time of writing), your publication ID, and two custom fields (phone, form name) created first.
Gmail or Google Workspace mailbox for the owner alert, connected to n8n by OAuth.
An n8n instance with a public HTTPS URL so Meta's webhook can reach it (n8n Cloud or self-hosted).

Built for

Questions before you buy

Can I use it with more than one Page or form?: Yes. One trigger subscribes to one Page and catches every form on it. A second Page means a second trigger node, which the guide shows how to add. If you only want certain forms, a filter on form ID sits right after the trigger.
Do I need to put the Meta app through App Review?: Not for your own Pages. An app left in development mode can pull leads from any Page you administer, and that is the setup the guide walks through. App Review only matters if you want the same app to serve Pages you do not own.
What happens if beehiiv rejects the call or the API key expires?: The run is marked failed in n8n and the included error workflow emails you the lead's details, so the person is never lost. Fix the credential, then re-run the failed execution from n8n's list. Meta also keeps the lead in Leads Center for 90 days as a backstop.
Does it run on Make or Zapier?: Both. The package includes a Make scenario and a Zap that follow the same steps. Facebook Lead Ads is a premium app on Zapier, so that route needs a paid Zapier plan.
Is a paid n8n plan required?: No. n8n Cloud's entry plan works, and the self-hosted community edition is free. The one hard requirement is a public HTTPS address for the webhook, which n8n Cloud provides and a self-hosted install needs a reverse proxy for.

Nearby on the shelf

Whole catalog