Facebook graph API token

Questions
1

Hello,

Is there a guide to connect n8n with Facebook Gaph API?

Do I have to create a new token for every Facebook page I want to post to?

And the max token life we can get is 2 months with the debug tool?

I would like to have a single token for all pages and to never expire.

Thanks for any hints

2

Hi @JackBauer

Hope you’re doing well :dizzy:

  1. Is there a guide to connect n8n with Facebook Graph API?
    Yes. n8n has official docs for the Facebook Graph API node and its credentials, which walk you through creating a Meta app and generating an App Access Token to use in n8n.[FB Graph node; FB Graph creds]

  2. Do I have to create a new token for every Facebook page I want to post to?
    The n8n docs only state that the Facebook Graph API credentials use an App Access Token; they don’t explicitly say whether you must create separate tokens per page.[FB Graph creds]
    A community example for posting to a page shows using a page token (not a user token) with the right permissions, but it doesn’t clearly state if one token can cover multiple pages.[Forum: post to page]
    So, based on the available sources, this point isn’t fully clarified.

  3. Is the max token life 2 months with the debug tool?
    The n8n docs don’t specify any exact token lifetime or a 2‑month limit; they only describe how to generate an App Access Token and use it.[Using app token]
    A community thread mentions that a page‑specific token can show as “does not expire” in Facebook’s token debugger, which suggests some tokens can be long‑lived or non‑expiring, but this behavior is defined by Facebook, not by n8n.[Forum: renewing token]

So, n8n provides the integration guide, but details about “one token for all pages” and exact token lifetimes are governed by Facebook’s own token rules and aren’t fully documented in the n8n sources.

3

Exactly, the n8n docs mention an app token which does not work for publishing on Facebook pages…

4

@JackBauer

the most stable workaround in n8n is to separate authentication from execution: use Page Access Tokens and manage them outside of the n8n credentials system.

By centralizing the page tokens in a database or data store, you can keep a single workflow that posts to N pages without exploding the number of credentials, injecting the correct token dynamically per page. If a token expires, automate the rotation — even if it appears as “never expiring”, it’s safer to treat it as temporary.

n8n itself doesn’t limit token lifetime; it will work as long as the token you send is valid.

5

But the facebook graph api node requires an access token which cannot be taken from outside n8n I believe.

6

@JackBauer

The Facebook Graph API itself only requires a valid access token in the request header.
n8n does not enforce where that token comes from, credentials are just a convenience layer.

If you need to manage Page Access Tokens externally or dynamically (for example, posting to multiple pages or handling rotation), the recommended approach is to use the HTTP Request node and inject the token at runtime via headers.

The Facebook node is designed around static credentials, which can be limiting for this use case, but this is a node design choice, not a Graph API or n8n runtime limitation.

Token lifetime and scope are defined entirely by Facebook, not by n8n.

7

Hi @JackBauer What i had used in the facebook graph API is the below documentation:

Hope this helps, Happy n8n-ng!