Overview
This node acts as a trigger for Facebook Lead Ads events by listening to webhook notifications from Facebook. It is designed to capture new lead submissions from specified Facebook Pages and Forms linked to those pages. When a user submits a lead form on Facebook, this node receives the event data and outputs it for further processing in an n8n workflow.
Common scenarios where this node is beneficial include:
- Automatically capturing and processing new leads from Facebook Lead Ads into CRM systems.
- Triggering follow-up workflows such as sending emails or notifications when a new lead is generated.
- Aggregating lead data for analytics or reporting purposes.
Practical example: A marketing team uses this node to listen for new leads submitted via their Facebook Lead Ads forms. Each time a lead is captured, the node triggers a workflow that adds the lead information to their customer database and sends a notification to the sales team.
Properties
| Name | Meaning |
|---|---|
| Due to Facebook API limitations, you can use just one Facebook Lead Ads trigger for each Facebook App | Notice informing users about the limitation of having only one Facebook Lead Ads trigger per Facebook App. |
| Event | The type of event to listen for. Only option available is "New Lead" which triggers when a new lead is submitted. |
| Page | The Facebook Page linked to the lead form. Can be selected from a list of pages or specified by ID. |
| Form | The specific lead form to monitor for submissions. Can be selected from a list of forms or specified by ID. |
| Options > Simplify Output | Boolean option to return either a simplified version of the webhook event (default: true) or the full raw data with all fields. |
Output
The node outputs JSON data representing the lead submission event. The structure depends on the "Simplify Output" option:
Simplified output (default):
An array of objects where each object contains:id: Lead IDdata: Key-value pairs of lead field names and their values extracted from the submissionform: Basic details about the form (id, name, locale, status)ad: Ad details (id, name)adset: Ad set details (id, name)page: Page details associated with the formcreated_time: Timestamp of lead creation
Full output:
Includes all fields from the lead data and form details without simplification, preserving the complete structure received from Facebook.
No binary data output is produced by this node.
Dependencies
- Requires a valid Facebook API OAuth2 credential with permissions to access lead ads data.
- Needs configuration of a Facebook App with webhook subscriptions enabled.
- The node manages webhook subscription lifecycle automatically but requires the Facebook App ID and secret.
- Environment must allow receiving incoming HTTP requests at the configured webhook URL.
Troubleshooting
Webhook subscription conflicts:
Error if another webhook subscription exists for the same Facebook App. Due to Facebook API limitations, only one webhook subscription per app is allowed.
Resolution: Delete existing webhook subscriptions in the Facebook App or use a different Facebook App.Signature verification failure:
Incoming webhook POST requests are verified using HMAC SHA256 with the Facebook App secret. If signatures do not match, the event is ignored.
Resolution: Ensure the correct Facebook App secret is used in credentials and that the webhook URL is correctly configured.Empty or missing lead data:
If no relevant lead data matches the configured page or form, the node returns empty output.
Resolution: Verify the correct Page and Form IDs are selected and that leads are being submitted to those forms.Permission errors:
If the Facebook OAuth2 credential lacks required permissions, the node will fail to subscribe or fetch lead data.
Resolution: Confirm the credential has appropriate scopes and the Facebook App is properly configured.