Facebook Leads Trigger: additional OAuth scopes needed

[spatialy]

Describe the bug
The current implementation cannot load a list of Pages when the user has been given permissions through a Business Manager, a common use-case when working with clients' assets where the permission access settings are not at the Page level but at the Business Manager level.

To Reproduce
Steps to reproduce the behavior:

1. Add permissions to a BM user through the BM system (the user cannot be directly on the Page Level permissions)
2. Add node and establish an auth permissions
3. Try to select/search this page in the node page list

This can be reproduced on the Facebook API Explorer. Do the same and see the pages you can get a page_token on the list, add business_management to the permissions list and refresh the user_token, and then the Pages you have access only through a Business Manager are correctly listed.

Expected behavior
All Facebook Pages listed, without regard to what level you get your access permissions.

SOLUTION
Add business_management to file packages/nodes-base/credentials/FacebookLeadAdsOAuth2Api.credentials.ts

Environment (please complete the following information):

• n8n Version: 1.14.0 cloud-hosted

[Joffcom]

Hey @spatialy,

I am closing this as you already created a PR and a topic on the forum here: https://community.n8n.io/t/facebook-lead-trigger-issue-with-permissions/32500/3

[janober]

Fix got released with n8n@1.16.0