Facebook Graph API Credential - Missing OAuth2 Fields, Only Shows Access Token Field

Questions
1

DSubject: Facebook Graph API Credential - Missing OAuth2 Fields, Only Shows Access Token Field

Hello n8n Support Team,

I’m having trouble setting up the Facebook Graph API credential for my n8n instance. My goal is to create a connection that automatically handles token refreshes so I can reliably post to a Facebook Page.

The Issue:

When I go to Credentials > Add credential and select “Facebook Graph API”, the screen that appears only has a single input field for a manual “Access Token”.

Based on the n8n documentation and support guides, I am expecting to see the standard OAuth2 setup screen with fields for:

  • App ID

  • App Secret

  • OAuth Callback URL

This screen is not appearing for me. Because of this, I am forced to manually generate a long-lived token from the Facebook Developer tools and paste it in. This token expires every 60 days, which is not a sustainable solution for my workflows.

What I’ve Confirmed:

  • My Facebook App is configured correctly on the developer portal. All permissions (pages_manage_posts, pages_show_list, etc.) are approved and the app is in Live mode.

  • I have successfully tested my connection using the Facebook Graph API Explorer and was able to fetch my page list and generate tokens without any issues. This confirms the problem is not with my Facebook App setup.

Could you please help me understand why the standard OAuth2 credential fields are not showing up in my n8n instance? I would like to use the proper method that allows for automatic token refreshes.

My n8n Information:

  • Version: Version 1.104.1

  • Deployment Method:

Thank you for your help.

2

Hello @Joe_Tinnerello

According to the docs, the Facebook Graph API node supports only app access token, it doesn’t support OAuth flow.

Supported authentication methods
App access token

Facebook Graph API credentials | n8n Docs

You can submit a Feature Request for the OAuth 2.0 types in the separate category: Latest Feature Requests topics - n8n Community

Use the HTTP Requests node if you want to use the OAuth 2.0 flow

3

Hi,

You won’t be able to use the built-in Facebook credentials for this purpose as it only supports app access.

The method we have previously used is to create a system account in Facebook business manager and then add a page as an asset to that, then you can generate a permanent token hitting something like:

https://graph.facebook.com/me/accounts?access_token={long-lived-user-token}

Meta has changed this flow a bunch of times and its quite obscure, but basically you need to authenticate as a user (with appropriate access to the given page and app) not an app, and then you can exchange your long lived token for a permanent token, which you can then use in n8n to manage a page.

I have not closely studied this guide, but at a glance this does describe more or less the process:

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.