Facebook Ads Insights API returning #200 permission error despite System User having full access

Hi Pabbly Support Team,

I am trying to use the Facebook Ads Insights / API request in Pabbly Connect to fetch insights for my Meta Ad Account.

Ad Account ID: 104283973725035
Ad Account: Abhishek Pal - FML
Pabbly Action: Facebook Ads Insights / API request

I am receiving this error:

(#200) Ad account owner has NOT granted ads_management or ads_read permission

I have already completed the following:

1. Created a Meta Developer App.
2. Connected the Ad Account to the app.
3. Created a System User.
4. Assigned the target Ad Account to the System User with Full Access.
5. Assigned the Developer App to the System User with Full Access.
6. Generated a new access token for the System User.
7. Granted ads_read permission.
8. The Ad Account ID is correct.

However, when I use the token in Pabbly and click Save & Send Test Request, I still receive the same #200 OAuthException.

Could you please check whether this is related to the current/upgraded Facebook Ads Insights integration/API implementation in Pabbly Connect, or whether any additional permission/parameter is required on the Pabbly side?

I can provide screenshots, workflow details, and the complete API response if required.

Please help me resolve this issue.

Hi Arpit,

Thanks for reaching out and for the detailed breakdown of the steps you've already completed.

The (#200) permission error you're seeing typically points to the token/permissions not being fully granted to the Pabbly connection. Based on what commonly resolves these Facebook-related permission issues, could you try the following:

1. Re-authorize the Facebook connection in your workflow by clicking Reconnect (or removing and re-adding the connection), and when the permission pop-up appears, allow ALL requested permissions without unchecking any (especially the ads-related scopes such as adsread/adsmanagement).
2. If a single Facebook connection is reused across multiple workflows, make sure the refreshed connection is re-selected everywhere it is used.
3. Verify the connected account still has admin/editor access to the Ad Account, and that app permissions haven't been revoked in Facebook's Business Settings.

If the error persists after a clean reconnection with full permissions, please let us know so we can check.

We'll review it further and assist you accordingly.