Resources · n8n integration

Facebook Graph API n8n integrationAutomate Facebook Graph API with n8n.

One node, the whole Graph API. The Facebook Graph API n8n integration ships a single generic operation: you pick the HTTP method, the API version, the node and the edge, and n8n signs the call with your Meta credential. No trigger node here, so a schedule or a webhook starts the run.

Try the Facebook Graph API integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Facebook Graph API n8n integration actually give you?

Most n8n app nodes hand you a menu of ready-made actions, one per object. This one does the opposite: it exposes the Graph API itself. The node carries 1 operation and 1 synthetic resource, and every request is described by the fields you fill in, the host, the method, the version, the node and the edge. n8n handles the authentication and returns Meta's JSON answer to the next step of the workflow.

That design takes a minute to get used to, and then it pays off. Anything the Graph API accepts on GET, POST or DELETE is reachable from the same node, with the same credential, without waiting for someone to add a dedicated action. The price of that freedom is that you write the path yourself, so keep Meta's reference open next to n8n the first few times.

Scheduled publishing is the most common shape. A content queue lives in Google Sheets, a Schedule Trigger picks the rows due today, and the Facebook node sends each one with the method set to POST, Node set to the Page ID and Edge set to feed. The response comes back as JSON, so the created post ID can go straight back into the sheet.

Media works the same way with two switches flipped. For a photo, keep the default host and target the /photos edge. For a video, set Host URL to graph-video.facebook.com, which exists for video uploads only, turn on Send Binary File and point Input Binary Field at the binary property coming from the previous node. Worth knowing before you debug for an hour: Instagram container endpoints such as /media do not take a binary file at all, they expect image_url or video_url as query parameters.

Reading is the third shape. A GET on a node, with the Fields and Query Parameters options filled in, returns exactly the properties you asked for and nothing else. Send that into Postgres for a weekly report, or post a short digest to Slack so the team sees the numbers without opening Business Manager.

Two limits are worth stating plainly. The node offers GET, POST and DELETE, so a call that needs another HTTP verb belongs in the HTTP Request node, which reuses the same credential through predefined authentication. And there is no Facebook Graph API trigger in n8n, which means nothing here reacts to a Facebook event on its own. Our n8n review covers how that changes workflow design, and the n8n training walks through building the first one.

Connect

How do you connect Facebook Graph API to n8n?

  1. 01

    Create a Meta app

    Both authentication methods start from a Meta for Developers account and an app. In the App Dashboard, select Create App, add an App name and an App contact email. For products in Meta's Business suite, pick Other as the use case, then Business as the app type. A business portfolio is optional at this point, so leaving it unselected is fine. Finish with Create app and add the products your workflow needs.

  2. 02

    Pick OAuth2 or an app access token

    OAuth2 needs the Facebook Login for Business product added to the app. Copy the OAuth Redirect URL shown in the n8n credential into Valid OAuth Redirect URIs, save, then take the App ID and App Secret from App settings and paste them as Client ID and Client Secret. Finish with Connect to Facebook Graph (App). An app access token skips all of that: generate it in the Graph API explorer with Get App Token, then Generate Access Token.

  3. 03

    Select the credential in the node

    A credential is created once in the n8n Credentials menu and reused in every workflow, so this step is a dropdown. In the node, Authentication tells n8n which of the two methods to apply, Access Token or OAuth2, and the matching credential appears in the list below it. Self-hosted or n8n Cloud makes no difference to the workflow itself. Ignore SSL Issues sits nearby and stays off in normal use.

Actions

What the node does, field by field

The Facebook Graph API node exposes one operation. For each one: the node as you configure it in n8n, the required fields, and our field notes.

01

Interacts with Facebook using the Graph API

execute

What you see in n8n

Notes & use cases

The only operation builds one Graph API request from your parameters and returns Meta's JSON answer.

Key parameters

  • Host URL: graph.facebook.com, or graph-video.facebook.com for video uploads only.
  • HTTP Request Method: GET to read, POST to create, DELETE to remove.
  • Graph API Version: Default, or a version pinned between v3.0 and v25.0.
  • Node: the Graph object targeted, not an n8n node: me or a Page ID, often {{ $json.id }}.
  • Edge: the collection attached to it, feed or videos.
  • Send Binary File: on POST, sends the file as multipart/form-data, named in Input Binary Field.
Use cases
publish a queued post on a Page feed, then read it back with GET.
Need help

Need help automating Facebook Graph API with n8n?

A person reads every message.

FAQ

Facebook Graph API and n8n, answered

01Is the Facebook Graph API n8n integration free?
Yes on the n8n side. The node ships with n8n, so there is nothing to install and nothing extra to pay, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow behaves the same in both. What sits on the Meta side is a separate matter: you need a Meta for Developers account and an app, and whatever Meta charges for the products you enable is between you and Meta. The node itself adds no fee, no quota and no middleman to the requests it sends.
02What credentials do you need for Facebook Graph API in n8n?
Two methods are supported, OAuth2 and an app access token, and both start with a Meta for Developers account plus a Meta app. OAuth2 requires the Facebook Login for Business product, a Client ID taken from the App ID, a Client Secret taken from the App Secret, and the n8n OAuth Redirect URL registered in Valid OAuth Redirect URIs. The app access token route is shorter: generate the token in the Graph API explorer with Get App Token, then paste it into the credential. Pick the one you want in the node's Authentication field. Either credential is created once and reused everywhere.
03What are the limits of the Facebook Graph API node?
It depends what you are missing. The node exposes GET, POST and DELETE, so any other HTTP verb has to go through the HTTP Request node, which can reuse the same credential through predefined authentication. There are also no per-object actions to browse: with 1 operation and 1 resource, you supply the node and the edge yourself, which means knowing the Graph API paths rather than picking from a list. Binary uploads work on edges that accept them, such as a Page's photos and videos, while Instagram container endpoints expect image_url or video_url as query parameters instead.
04Does Facebook Graph API trigger n8n workflows in real time?
No. This integration has no trigger node, so nothing on the Facebook side starts a run by itself. The workflow needs its own starting point. A Schedule Trigger fires at a fixed interval and suits publishing queues, reporting and anything that can wait for the next pass. An n8n Webhook gives you a URL that another service calls, so an approval tool or an internal app can start the run the moment something is ready. A trigger from another tool works too, for instance a new row somewhere upstream, with the Facebook node placed after it.
05n8n or Make for Facebook Graph API?
It depends on four things, and price is only one of them. Make is hosted by Make, with no self-hosting option, and bills per operation, so a workflow that loops over many items has a cost that grows with volume. n8n runs on n8n Cloud or on your own server through Docker or npm, which matters when the data passing through the workflow has to stay on infrastructure you control. Visual logic differs too, and that is mostly taste. For this node specifically, the generic Graph API approach rewards whoever is comfortable reading Meta's reference.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations