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.

Facebook Ads Insights connection not appearing in Connections & #200 permission error despite System User having Full Access
Hi Pabbly Support Team,

I am trying to use Facebook Ads Insights → Get Ad Account Insights in my Pabbly workflow to fetch daily insights for my Meta Ad Account.

My workflow action is available and working as an action inside the workflow, but I am facing an issue with the Facebook Ads Insights connection.

Ad Account Details:

• Ad Account ID: 104283973725035

• Ad Account Name: Abhishek Pal - FML

• Pabbly Action: Facebook Ads Insights → Get Ad Account Insights

Issue 1 — Permission Error

When I test the Facebook Ads Insights request, I receive:

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

I have already completed the following on Meta:

1. Created the 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.

5. System User has Full Access to the Ad Account.

6. Assigned the app to the System User.

7. Generated a new access token.

8. Granted the required ads_read permission.

9. Verified that the Ad Account ID being used in Pabbly is correct.

Issue 2 — Facebook Ads Insights connection is missing

The bigger issue is that when I go to:

Pabbly Connect → Settings → Connections → Add Connection

and search for Facebook Ads Insights, the app does not appear in the available connection list.

However, inside my existing workflow, I can select:

Facebook Ads Insights → Get Ad Account Insights

So the application/action is available inside the workflow, but I cannot find/create the corresponding connection from the Connections section.

I also tried reconnecting the existing connection from the workflow, but clicking the connection does not properly open the authentication/reconnection flow. I receive:

Please provide authentication details.

Meta Business setup

I have also verified the Meta Business settings:

• System User: daily-reportsystem

• System User has Full Access to the target Ad Account.

• The Pabbly/Test app is assigned to the System User.

• The target Ad Account is connected to the app.

• The Facebook Page and Ad Account assignments have also been checked.

Because all the required Meta-side permissions and asset assignments appear to be correctly configured, I suspect there may be an issue with the Facebook Ads Insights OAuth/connection integration in Pabbly Connect, especially because the app/action is available inside the workflow but is missing from the Connections section.

Request

Could you please check:

1. Whether Facebook Ads Insights connection/OAuth is currently working correctly on Pabbly Connect.

2. Why Facebook Ads Insights is not appearing under Settings → Connections → Add Connection.

3. Why my existing Facebook Ads Insights connection cannot be re-authenticated.

4. Whether there is any issue with the current Pabbly integration causing the #200 ads_read/ads_management error.

5. If required, please reset/remove the existing Facebook Ads Insights connection from your side so I can create a fresh connection.

I can provide screenshots of the Meta Business settings, System User permissions, access token permissions, Pabbly workflow and the exact API response if required.

Thank you.

Pabbly_Facebook_Ads_Insights_Screenshots.pdf (192.3 KB)

Hi Arpit,

Thank you for providing the additional details and screenshots.

To investigate and resolve both the permission error and the connection issue directly with you, we would like to inspect your workflow and Meta settings in real-time.

Please schedule a live troubleshooting meeting using this link: 👉 Schedule a Meeting

We will review your workflow setup during the session and assist you in getting the Facebook Ads Insights connection re-authenticated and running smoothly.

Looking forward to connecting with you!

Hi Hrishabh,
Thanks for the update.

At the moment, I would prefer to troubleshoot this issue through the support forum/email rather than scheduling a live meeting.

Could you please review the screenshots and details already provided and guide me with the exact steps required to resolve the Facebook Ads Insights connection/authentication issue?

If you need any additional screenshots, settings, error logs, or details from my side, please let me know and I will provide them.

Thanks.

Hi Arpit,

Thank you for clarifying.

We verified the token configuration against Meta’s API endpoints (/me/permissions and /debug_token). The inspector output confirms:

• Current Token Scopes: read_insights and public_profile

• Missing Scopes: ads_read or ads_management

While read_insights grants permission to fetch organic Page and App insights, the Meta Marketing API (/insights) specifically requires the ads_read permission to query Facebook Ad Account performance data. Without it, Meta returns the #200 OAuthException.

Step-by-Step Resolution

Step 1: Generate a Token with the ads_read Scope

1. Log into your Meta Business Settings.

2. In the left sidebar, navigate to Users $\rightarrow$ System Users.

3. Select your System User (daily-reportsystem).

4. Click Generate New Token.

5. Select your App from the dropdown.

6. Under the permissions list, scroll down and check ads_read (or ads_management).

7. Click Generate Token and copy the newly generated access token.

Step 2: Confirm Ad Account Asset Assignment

1. While still under System Users $\rightarrow$ daily-reportsystem, click Add Assets.

2. Select Ad Accounts on the left menu, then choose Ad Account 1042839737275035 (Abhishek Pal - FML).

3. Ensure View Performance or Full Control access is assigned to the user.

4. Click Save Changes.

Step 3: Update the Token in Pabbly Connect

1. Open your workflow in Pabbly Connect (Meta Daily Ad Account Report).

2. Go to the Facebook Ads Insights $\rightarrow$ Get Ad Account Insights action step.

3. Paste the new System User token directly into the Access Token field.

4. Click Save & Send Test Request.

Regarding Issue 2 (Connection Management)

App actions like Facebook Ads Insights utilize direct, API-key/Token-based authentication fields built into the action card itself, rather than standard OAuth-redirect popups.

Because connection management for API Token actions is handled directly inside the workflow's Access Token input field:

• The app does not maintain a separate entry under Settings --> Connections.

• To update or refresh credentials at any time, simply paste your updated Meta Access Token into the workflow field and click Save.

Please follow these steps to update your access token and test the action step. Let me know if you run into any further issues!

Hi Arpit,

Thank you for clarifying.

We verified the token configuration against Meta’s API endpoints (/me/permissions and /debug_token). The inspector output confirms:

• Current Token Scopes: read_insights and public_profile

• Missing Scopes: ads_read or ads_management

While read_insights grants permission to fetch organic Page and App insights, the Meta Marketing API (/insights) specifically requires the ads_read permission to query Facebook Ad Account performance data. Without it, Meta returns the #200 OAuthException.

Step-by-Step Resolution

Step 1: Generate a Token with the ads_read Scope

1. Log into your Meta Business Settings.

2. In the left sidebar, navigate to Users --> System Users.

3. Select your System User (daily-reportsystem).

4. Click Generate New Token.

5. Select your App from the dropdown.

6. Under the permissions list, scroll down and check ads_read (or ads_management).

7. Click Generate Token and copy the newly generated access token.

Step 2: Confirm Ad Account Asset Assignment

1. While still under System Users --> daily-reportsystem, click Add Assets.

2. Select Ad Accounts on the left menu, then choose Ad Account 1042839737275035 (Abhishek Pal - FML).

3. Ensure View Performance or Full Control access is assigned to the user.

4. Click Save Changes.

Step 3: Update the Token in Pabbly Connect

1. Open your workflow in Pabbly Connect (Meta Daily Ad Account Report).

2. Go to the Facebook Ads Insights -->Get Ad Account Insights action step.

3. Paste the new System User token directly into the Access Token field.

4. Click Save & Send Test Request.

Regarding Issue 2 (Connection Management)

App actions like Facebook Ads Insights utilize direct, API-key/Token-based authentication fields built into the action card itself, rather than standard OAuth-redirect popups.

Because connection management for API Token actions is handled directly inside the workflow's Access Token input field:

• The app does not maintain a separate entry under Settings --> Connections.

• To update or refresh credentials at any time, simply paste your updated Meta Access Token into the workflow field and click Save.

Please follow these steps to update your access token and test the action step. Let me know if you run into any further issues!