Fix: n8n Meta Lead Ads webhook not triggering
n8n Meta Lead Ads webhook failures occur at three boundaries: the test URL, the Page's leadgen subscription, and OAuth access. Check them in order.
Last updated: September 30, 2026 · Tested on n8n 1.x / Meta Lead Ads API · ~6 min read
Symptoms — what you're seeing
- A person submits a Facebook or Instagram Lead Ad form, but the n8n workflow does not start
- Meta's webhook verification fails with a callback, token, or GET-request error
- The Facebook Lead Ads Trigger works when you test it manually, but real leads never appear
- The Facebook Page does not appear in the Page selector inside the n8n trigger node
- n8n receives a webhook execution, but the Google Sheets node does not append a lead row
Why this happens
There are two separate operations in this integration. Meta first sends a webhook notification to n8n when a lead is created. n8n then uses the authorized Meta account to retrieve the lead fields and pass them to the next node. A successful webhook verification does not prove that lead retrieval or Google Sheets mapping works.
1. n8n is exposing the test URL. The webhook-test URL is temporary and only listens while you execute a workflow manually. Meta's verification request is a GET request, and the test listener is not the production endpoint. Use the active workflow's production URL containing /webhook/, not /webhook-test/.
2. The Meta Page is not subscribed to leadgen. A valid callback does not establish a Page subscription for the lead-generation event. Meta's Webhooks area has an app-level callback and a separate Page subscription. Both must be configured.
3. OAuth access stops at the test user. In Development mode, admins, developers, and testers can create test leads successfully. Real leads from people outside the app roles require the correct production access, Business verification, Page access, and lead-retrieval permissions. The exact review requirements depend on Meta's current app configuration, so confirm the current permission and App Review names in Meta's own documentation before relying on them.
4. Agency and client assets belong to different Business Managers. When the agency owns the Meta app but the client owns the Facebook Page and Ad Account, both assets must be shared with the app-owning Business Manager. Sharing only the Page is not enough when the app also needs ad-account or lead access.
5. The webhook notification arrives, but the downstream mapping is wrong. Meta's notification contains an identifier that n8n uses to retrieve the full lead. When the credential cannot retrieve that lead, or the Google Sheets node maps fields that are not present in the incoming item, the trigger looks broken even though the webhook reached n8n.
Use the same diagnostic split as other webhook failures: first prove that the request reaches n8n, then prove that Meta lead retrieval works, and only then inspect the Google Sheets mapping. When you are connecting another CRM or webhook system, the GoHighLevel to n8n webhook setup follows the same production-versus-test URL distinction.
Stuck on this already? Book a 30-min call and I'll inspect the callback, Page subscription, and first n8n execution with you. You can also email Basit.
The fix, step by step
- Confirm that n8n is publicly reachable over HTTPS. Open the n8n instance from outside your network and confirm that its public URL resolves with a valid certificate. Meta cannot verify a localhost URL, a private network address, or a self-signed certificate. When a reverse proxy or WAF sits in front of n8n, allow the webhook route and preserve GET and POST requests.
- Create the Meta app under the correct Business Manager. In Meta for Developers, open the app connected to the Business Manager that owns the integration. Confirm that the Facebook Page and its advertising account are available to that Business Manager. In an agency setup, confirm asset sharing on both the client and agency sides.
- Check Business verification and app roles. In Business Settings, check the Business verification status. The OAuth user authorizing n8n must have access to the Page and must be an administrator, developer, or tester of the Meta app while you are testing. A Development-mode test is not proof that an external lead will work in production.
- Recreate or reauthorize the n8n credential. In n8n, open the Facebook Lead Ads OAuth2 credential and copy the OAuth Redirect URL shown there. Add that exact URL to the Meta app's valid OAuth redirect URIs. Confirm the App ID and App Secret, then authorize again with the Facebook user that can manage the target Page. Credential label names and the Meta Login product location can shift between versions, so confirm both against your installed n8n version and current Meta app.
- Build the smallest possible workflow. Add a Facebook Lead Ads Trigger and select the target Page. Use the New lead event. For the first test, connect it directly to a debug-friendly node or a Google Sheets node with a simple append operation. Do not add AI enrichment, CRM updates, or branching until the raw lead reaches n8n.
- Activate the workflow before configuring Meta's callback. Turn on the workflow in n8n. Open the Facebook Lead Ads Trigger and copy its production URL. It must contain
/webhook/and must not contain/webhook-test/. The workflow must remain active while Meta verifies and calls the endpoint. - Configure the callback and Page subscription in Meta. In the Meta app's Lead Ads or Webhooks configuration, select the Page product and enter the n8n production URL. Enter the verification token required by the n8n trigger, then run Meta's verification. After the callback is saved, find the
leadgenfield and enable the Page subscription. Meta periodically moves and renames this configuration UI, so confirm the current labels in Meta's own interface if the steps above don't match what you see. - Test the webhook and the lead retrieval separately. Use Meta's test control for the
leadgenfield when Meta exposes it in the current UI, and watch the active n8n workflow executions. Then create a test lead with Meta's Lead Ads testing tool or submit a real test form using a test contact. These are different tests: the webhook test checks delivery to the callback, while a lead-form submission checks Page subscription and lead retrieval. - Inspect the first n8n execution item. Confirm that the trigger received an item for every lead instead of assuming that the first item represents the whole submission. Open the execution data and identify the fields exposed by the installed Facebook Lead Ads Trigger version. Map those actual fields into Google Sheets. Do not guess field names from the form labels; custom questions and contact fields can be returned with different keys.
- Configure Google Sheets only after the trigger works. In Google Sheets, use the target document and the exact worksheet. Choose Append Row and map each destination column to the corresponding field from the trigger output. Run one test lead, check the resulting row, and then add downstream CRM or notification nodes.
# Replace <your-n8n-host> and <your-production-path> with the real # host and production webhook path from the active n8n workflow. # This checks reachability; it does not replace Meta's signed verification. curl -i "https://<your-n8n-host>/webhook/<your-production-path>"
The curl response alone does not prove that Meta can complete verification or that the Page is subscribed. Use it only to separate DNS, TLS, firewall, and routing failures from Meta permission failures.
Common variations
- “It says the webhook is not registered for GET requests.” The URL is the n8n test URL, the workflow is inactive, or the request is routed to a different n8n instance. Switch to the active production URL and verify that the reverse proxy forwards GET requests.
- “The Page is missing from the Facebook Lead Ads Trigger.” Reauthorize with a user who can manage that Page. Then check Page access, Business Manager asset sharing, and the app role. The Page selector is not a list of every Page visible in the browser; it is limited by the authorized token.
- “The webhook test passes but a real form submission does nothing.” Check the
leadgenPage subscription, Business verification, production permissions, and whether the ad uses the Page and form you configured. A callback verification is not a lead event. - “n8n receives an execution but fields are empty.” Inspect the complete item output and the lead-retrieval error. Custom questions may use different field keys from the visible question text. Map the fields exposed by the trigger instead of hard-coding labels from the form editor.
- “The lead reaches n8n but does not reach Google Sheets.” The Meta side is already working. Check the Google credential, spreadsheet permissions, worksheet name, column mapping, and the failed Google Sheets node execution.
- “The integration worked for admins but not for ad leads.” That is an app-mode or permission boundary. Test users produce misleading results in Development mode. Verify the Business, Page, Ad Account, app review status, and lead-retrieval access together.
When this isn't the issue
When the Facebook Lead Ads Trigger has a successful execution, stop changing the Meta webhook. The failure is downstream.
- Open the execution and confirm that the trigger returned the lead item you expected.
- Check whether the Google Sheets node is using the correct document, worksheet, and append operation.
- Check Google OAuth scopes and whether the authorized user still has Editor access to the spreadsheet.
- When a Code, IF, Filter, or Set node sits between the trigger and Google Sheets, disable it temporarily and test the direct connection.
- When your workflow runs but duplicates rows, inspect retries and any second active workflow subscribed to the same Page. For a broader n8n reliability checklist, see the production webhook setup guidance before adding more retry logic.
Stuck on this for more than 30 minutes? Book a 30-min call. I'll get on Zoom, look at your workflow, and either fix it on the call or scope what it'll take. No upsell, no decks. You can also email Basit.
Related pages
Need this workflow customized or debugged? Book a 30-min scope call →
Stuck configuring this workflow?
I build and fix n8n workflows for agencies and SaaS teams. 30-minute scope call — bring the problem, leave with an estimate.