Facebook Pages – “Get Page Details” & “Custom API Request (Beta)” not injecting Page token / fields correctly

[avielchik]

Consent to Access & Modify

I don't authorize Pabbly Support to log in to my account.

When using Facebook Pages → Get Page Details, the module fails to substitute the fields parameter correctly. Even with simple input like id,name, the request sent to Meta contains a literal {{fields}}, resulting in a Graph API error:

Syntax error: Expected end of string instead of 'd' at character 6: {{fields}}

Additionally, Facebook Pages → Custom API Request (Beta) consistently injects a User access token instead of a Page access token, even when:

• A Page is explicitly selected in prior steps
• A valid Page Access Token is available in outputs from other Facebook Pages actions

This causes Graph API errors such as:

User Access Token Is Not Supported
A Page access token is required for this call

It is currently impossible to reliably fetch a Page feed (/PAGE_ID/feed) using Facebook Pages modules, forcing me to bypass it with generic HTTP modules.

 

[ArshilAhmad]

Hi @avielchik,

Could you please share the Workflow URL where you have this concern?

Thanks & Regards,
Arshil Ahmad
Customer Support Associate
Pabbly.com
Rate your support

 

[avielchik]

Any workflow behaves the same, create a workflow and test it yourself.

 

[ArshilAhmad]

When using Facebook Pages → Get Page Details, the module fails to substitute the fields parameter correctly. Even with simple input like id,name, the request sent to Meta contains a literal {{fields}}, resulting in a Graph API error:

Syntax error: Expected end of string instead of 'd' at character 6: {{fields}}

We were able to replicate this issue in this test workflow:

Pabbly

connect.pabbly.com

Please allow us some time to look into this concern. We will get back to you with an update soon.

Additionally, Facebook Pages → Custom API Request (Beta) consistently injects a User access token instead of a Page access token, even when:

• A Page is explicitly selected in prior steps
• A valid Page Access Token is available in outputs from other Facebook Pages actions

This causes Graph API errors such as:

User Access Token Is Not Supported
A Page access token is required for this call

For this, please share the cURL command and the API documentation for the endpoint you’re trying to execute. Also, share the workflow URL where you attempted to execute the endpoint.

Thanks & Regards,
Arshil Ahmad
Customer Support Associate
Pabbly.com
Rate your support