Facebook Lead Ads form dropdowns now load correctly
Facebook Lead Ads Trigger nodes can now load forms after selecting a page, eliminating the need for users to manually configure permissions through Meta's developer tools.
When setting up a Facebook Lead Ads Trigger node, selecting a Page worked fine, but the subsequent Form dropdown failed with a permission error. This happened because the OAuth2 credentials were missing the pages_read_engagement scope needed to retrieve form data. Users had to discover and manually add this permission through Meta's Graph API Explorer—a workaround that shouldn't be necessary.
The fix adds pages_read_engagement to the default scope list in the Facebook Lead Ads OAuth2 credentials. Now forms load automatically after page selection, with no manual permission configuration required.
This change affects the n8n nodes-base package, specifically the Facebook Lead Ads credential configuration used by the trigger node.
View Original GitHub Description
Summary
The Facebook Lead Ads Trigger Node fails when trying to load the Form selection dropdown. Selecting a Page works, but the subsequent Form dropdown returns the following error:
Could not load list 400 - (#100) Object does not exist, cannot be loaded due to missing permission or reviewable feature, or does not support this operation. This endpoint requires the 'pages_read_engagement' permission or the 'Page Public Content Access' feature or the 'Page Public Metadata Access' feature.
This is because the pages_read_engagement scope is missing from the OAuth2 credential configuration. This PR adds it to the default scope list.
Steps to reproduce
- Create a new Facebook Lead Ads Trigger node
- Create new OAuth2 credentials and connect them
- In the node configuration, select a Page from the dropdown — this works fine
- Try to select a Form from the dropdown below — this fails with the error above
Workaround (without this fix)
The issue can be worked around by manually adding the pages_read_engagement permission to the app and user via the Meta Graph API Explorer. However, this is hard to discover and shouldn't be necessary since the credential should request all required scopes automatically.
Review / Merge checklist
- PR title and summary are descriptive. (conventions)
- Docs updated or follow-up ticket created. — N/A, no docs change needed for a scope fix
- Tests included. — N/A, this is a single scope string addition with no logic change