Resources · n8n integration

Facebook Lead Ads n8n integrationAutomate Facebook Lead Ads with n8n.

A form submitted on Facebook can start a workflow seconds later. The Facebook Lead Ads n8n integration is a trigger carrying 1 event, newLead, scoped to one page and one form. Built for teams who want the lead sitting in their own tools, not waiting to be fetched.

Try the Facebook Lead Ads integration on n8n

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Facebook Lead Ads n8n integration actually do?

It turns a Facebook lead form into the starting point of an automation. n8n registers a webhook, a URL that Facebook calls the moment someone submits the form you are watching, and hands the submission to the workflow as data you can filter, enrich and write anywhere. One trigger node, 1 event, and everything after it is built from the nodes you already use.

The lead is in the spreadsheet before anyone thinks to check. A campaign runs, submissions come in at odd hours, and a row appears in Google Sheets for each one. Add a message to a Slack channel on the same run and the sales team reads the lead instead of hunting for it.

The first reply goes out while the prospect is still on their phone. The trigger fires, a Gmail node sends the confirmation, and the workflow logs that it went out. Response time stops depending on who happens to be at a desk.

Leads arrive sorted rather than raw. Send the submission through an OpenAI node, let it classify the request, and write the result where it belongs. A workflow that reads one value with an expression like {{ $json.field }} can branch on it too. Same run, no extra tooling.

The trigger watches one page and one form, so a second form means a second workflow with its own selection. That usually suits the job, since the follow-up after a quote request has little in common with the follow-up after a guide download. Splitting them early saves untangling them later.

Building this for the first time? A useful order: pick the page, pick the form, activate the workflow, then fire a demo submission with the Lead Ads Testing Tool and open the execution that appears. You look at the real event once, and every node you add afterwards is written against something you have actually seen rather than something you assumed.

Anything else you need from Meta's API goes through the HTTP Request node, which calls any endpoint while reusing the same credential through its predefined authentication. And if you are still weighing platforms before you build, the n8n review covers the trade-offs in more depth.

Connect

How do you connect Facebook Lead Ads to n8n?

  1. 01

    Create a Meta app

    Authentication runs on OAuth2, so the first stop is a Meta for Developers account. In the App Dashboard, select Create App. You can connect a business portfolio or pick the option to skip it for now, then select Other and Business as the app type. Fill in an App name and an App contact email, select Create app, and add the Facebook Login for Business product.

  2. 02

    Pair the redirect URL with the app keys

    Open the credential in n8n and copy its OAuth Redirect URL. Back in the Meta app, under Client OAuth settings, paste it into Valid OAuth Redirect URIs. Then go to App settings > Basic: the App ID becomes the Client ID in n8n, the App Secret becomes the Client Secret. Save, connect, and the credential is reusable in every workflow you build afterwards.

  3. 03

    Take the app live

    A connected credential is not the finish line. In App settings > Basic, enter a Privacy Policy URL and save, then switch App Mode from Development to Live. Facebook Login for Business also needs Advanced Access for public_profile: request it under App Review > Permissions and Features and complete business verification. The Lead Ads Testing Tool then fires demo submissions so you can watch the workflow run.

Triggers

What starts the workflow?

Facebook Lead Ads Trigger is the node that starts a workflow when something happens in Facebook Lead Ads. It listens to 1 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Facebook Lead Ads account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

new.*1

    Configuration notes

    01Set Up the Facebook Lead Ads TriggerTwo resource pickers do most of the work. The node holds one Facebook page and one form belonging to that page, then waits. The webhook is registered when you activate the workflow, so nothing lands while the canvas is still a draft.

    Two resource pickers do most of the work. The node holds one Facebook page and one form belonging to that page, then waits. The webhook is registered when you activate the workflow, so nothing lands while the canvas is still a draft.

    Key parameters

    • Page: the page linked to the form you want leads from. n8n lists the pages the credential can reach, so there is no ID to paste by hand.
    • Form: the form n8n monitors, and the one it fetches lead details from on each submission. The list depends on the page above, so choose the page first.
    • Event: this node carries 1 event, newLead. Nothing to weigh up.
    • Simplify Output: found under Options. Switched on, n8n returns a simplified version of the webhook event instead of all its fields.
    Use cases
    one form on a seasonal campaign, wired once and left running for as long as the campaign does.
    02New LeadOne submission, one item in the workflow. newLead fires when someone completes the form you selected, and the nodes downstream read the data with an expression such as {{ $json.field }}, a reference to a field on the incoming item. Since Facebook calls the n8n URL, the lead shows up within seconds rather than on a schedule.

    One submission, one item in the workflow. newLead fires when someone completes the form you selected, and the nodes downstream read the data with an expression such as {{ $json.field }}, a reference to a field on the incoming item. Since Facebook calls the n8n URL, the lead shows up within seconds rather than on a schedule.

    Key parameters

    • Simplify Output: leave it off for the first test run. You see the full event, you spot what the rest of the flow actually needs, and you can switch it on afterwards if only a handful of values matter.
    When to use it
    whenever the gap between submission and first contact matters more than formatting.
    Use cases
    a workshop sign-up where the confirmation has to go out immediately, and a quote request routed to whichever rep covers that territory.
    Need help

    Need help automating Facebook Lead Ads with n8n?

    A person reads every message.

    FAQ

    Facebook Lead Ads and n8n, answered

    01Is the Facebook Lead Ads integration free in n8n?
    Yes on the n8n side. The trigger node ships with n8n, so there is nothing to install and no add-on to buy, and it behaves the same way on n8n Cloud, the hosted offer run by n8n, as on an instance you host yourself with Docker or npm under the Community Edition and its Sustainable Use licence. A workflow built in one runs unchanged in the other. What a Facebook Lead Ads campaign itself costs is a separate question and sits outside what n8n charges for, so budget for it the way you already do.
    02What credentials do you need for the Facebook Lead Ads trigger?
    OAuth2, and only OAuth2. You need a Meta for Developers account and a Meta app built with the Facebook Login product or the Facebook Login for Business product, which gives you the Client ID and Client Secret that n8n asks for. They come from App settings, Basic: App ID and App Secret. You also paste the OAuth Redirect URL shown in n8n into Valid OAuth Redirect URIs on the Meta side. Before the trigger works, the app needs a Privacy Policy URL, Live mode, Advanced Access for public_profile and business verification. The credential is created once and reused everywhere.
    03What are the limits of the Facebook Lead Ads n8n integration?
    It depends what you are counting. The trigger carries 1 event and watches one page and one form at a time, so covering several forms means several workflows, each with its own selection. Facebook Lead Ads also registers a single webhook URL per app, which means the test URL and the production URL overwrite each other and only one of them receives events. Anything else you want from Meta's API is reachable through the HTTP Request node, which calls any endpoint and reuses the same credential through its predefined authentication.
    04Does the Facebook Lead Ads trigger fire in real time?
    Yes. This trigger runs on a webhook, meaning n8n registers a URL with Facebook when you activate the workflow, and Facebook calls that URL each time the form is submitted. The event arrives within seconds, with no polling and no interval to configure. The practical consequence is that a draft workflow receives nothing at all: the registration happens at activation. Publish the workflow, submit a test entry with the Lead Ads Testing Tool, and you should see the execution appear on its own without touching the canvas.
    05n8n or Make for Facebook Lead Ads?
    It depends on four things, and price is only one of them. Make is a hosted automation platform with no self-hosting option, billed per operation, so cost tracks volume and the lead data lives on their infrastructure. n8n runs on Cloud or on a server you control, which matters when lead data carries constraints you have to answer for. The third criterion is the visual logic and how comfortable your team is reading it. The fourth is what happens past the catalogue: with n8n, the HTTP Request node covers whatever the dedicated node does not, using the same credential.
    Hack'celeration Lab

    Get our weekly integration tips.

    No spam. Unsubscribe anytime.

    Same platform

    Other docs you might need on this stack.

    Browse all integrations