Back to Blog
6 min read

n8n Facebook Post Automation: Schedule Page Posts

Post and schedule to a Facebook Page from n8n: the Graph API node with your own Meta app, or our node with no app. Plus why Groups fail.

n8n Facebook Post Automation: Schedule Page Posts

Short answer: n8n can post and schedule to a Facebook Page in two ways. n8n's own Facebook Graph API node calls Meta directly, but n8n says "you'll need a Meta for Developers account and a Meta app." Or you can send the post through Status 200 Uploads with our n8n node or an HTTP Request node: no Meta app of your own, and you can schedule it "up to 365 days ahead." Facebook Groups are a different story: Meta removed the Groups API on April 22, 2024, so no n8n workflow can post to a group.

Key Takeaways

Point Details
Two routes n8n's Facebook Graph API node (your own Meta app), or our node / HTTP Request (our Meta app).
Scheduling Our node: "When is Now, or At a Set Time", up to 365 days ahead. API: post.scheduledFor with a time zone.
Where posts go To a Facebook Page. Our Facebook page says posts go "To the Facebook Page of the connection."
Post types "Text on its own, one photo, several photos in one post, a video or a Reel."
Reels "Facebook takes Reels of 3 to 90 seconds."
Groups Meta deprecated publish_to_groups; "These permissions, features, and abilities will be removed April 22, 2024."
Plan Facebook and our n8n node are "On every plan, Free included."

Option 1: n8n's Facebook Graph API node

n8n ships a built-in Facebook Graph API node. It is a thin layer over Meta's API: you choose the Graph API version, a Node "for example /<page-id>/feed", and an edge. For videos you switch the host: "Video: Requests are passed to the graph-video.facebook.com host URL. Used for video upload requests only."

The catch is the setup. n8n's credentials page says: "Regardless of the authentication method you choose, you'll need a Meta for Developers account and a Meta app." You create the app in Meta's App Dashboard, pick a use case and an app type, and handle the Page tokens and permissions yourself. For a developer who already has a Meta app, that's fine. For a team that just wants posts on a schedule, it's a lot of setup for one workflow.

Option 2: our n8n node (no Meta app)

Our community node, @status200uploads/n8n-nodes-status200uploads, "publishes, schedules, checks and cancels posts" with your rl_ API key, as our n8n integration page says. You sign in on Facebook once inside Status 200 Uploads and pick the Page. Our Facebook page explains why there is no app review for you: "our Meta app publishes for you, so there is no app review to go through on your side."

To schedule a Page post from a workflow:

  1. Install the node. "On n8n Cloud, an owner or admin opens the nodes panel, searches for Status 200 Uploads and clicks Install (n8n verified the node on 26 October 2026)." On self-hosted n8n, install it under Settings, Community Nodes.
  2. Add your key. Create a "Status 200 Uploads API" credential and paste your rl_ key.
  3. Add a Post: Create node. Pick the account, platform Facebook, the text and the media. "When is Now, or At a Set Time."
  4. Pick the time. Post: Create can "Publish a post now, schedule it (When: At a Set Time, up to 365 days ahead) or only check it (Check Only (Dry Run)), with an automatic Idempotency-Key."
  5. Cancel if plans change. Post: Cancel can "stop a scheduled or queued post that has not gone out."

One node sends one post to one network, so to post the same update to Facebook and LinkedIn, add one Post: Create node per network.

Option 3: an HTTP Request node (any n8n)

If you can't install community nodes, the HTTP Request node calls the same API. Our Facebook page gives the setup: method POST, address https://status200uploads.com/api/v2/posts, and headers "Authorization Bearer rl_your_key, Content-Type application/json, and an Idempotency-Key such as {{ $json.id }}-facebook, so a retried execution never posts twice to the Page."

Here is the body for a photo post, with a time added so it is scheduled instead of sent now:

{
  "post": {
    "accountId": "@yourpage",
    "platform": "facebook",
    "scheduledFor": "{{ $json.publishAt }}",
    "content": {
      "text": "{{ $json.message }}",
      "mediaID": ["{{ $json.photoId }}"]
    },
    "facebook": { "postType": "photo" }
  }
}

publishAt must carry a time zone, like 2026-11-06T09:00:00+01:00. Our API docs are strict about it: "A time without a zone (even one in the past), a value that is not a date and time, or a time more than 365 days ahead is refused with 400 scheduled_for_invalid". More than a minute ahead, "the post is scheduled for that time (202 scheduled), up to 365 days ahead and at most 500 posts waiting per account". Drop scheduledFor to post now, and "Drop the mediaID line and the post becomes a text post."

Two settings to get right in n8n:

  • Retries. Our n8n page says to add the Idempotency-Key header "before you turn on Retry On Fail (Max Tries 5, Wait Between Tries 5000 ms). Without the header, turn Retry On Fail off."
  • Spacing. "Leave at least a minute between two posts to the same Page: the answer warns when two are due within 20 seconds."

For the general n8n setup across every network, see our n8n posting guide.

What you can post to a Facebook Page

These limits are from our Facebook page, checked on 26 October 2026:

Post type How to send it Limit
Text No media field, or postType text Caption up to 63,206 characters
Photo One image, postType photo 10 MB checked in the dashboard; through the API, Facebook decides
Several photos Several images in one post Published "together as one post on the Page"
Video One video file Up to 5 GB
Reel One video, postType reel 3 to 90 seconds

A Reel sent with a picture is stopped early: "a Reel or a video post sent with a picture is refused before Facebook is called." The error is media_wrong_for_post_type.

Can n8n post to a Facebook group?

No, and it's not an n8n limit. Meta's Graph API v19.0 changelog lists the Groups API as deprecated, including the publish_to_groups and groups_access_member_info permissions, and says: "These permissions, features, and abilities will be removed April 22, 2024." That applies to n8n's Graph API node, to us, and to every other tool that uses Meta's API.

Personal profiles are out too. Our Facebook FAQ answers "Can I post to my personal Facebook profile?" with "No. Posts go to the Facebook Page of the connection, the Page you chose when you connected Facebook."

When a scheduled Facebook post fails

The two errors you're most likely to see in n8n, from our Facebook page:

  • 401 reconnect_required: "Facebook no longer accepts the saved sign-in, or the connection has expired." Reconnect Facebook under Connections and send it again.
  • 500 platform_error: "Facebook answered with a server error that named no code." Send it again once, "with the same Idempotency-Key."

FAQ

Can n8n schedule Facebook posts? Yes. With our n8n node, set When to At a Set Time, up to 365 days ahead. With an HTTP Request node, add post.scheduledFor with a time zone. n8n's own Graph API node calls Meta directly, with your own Meta app.

Do I need a Meta developer app to post to Facebook from n8n? For n8n's Facebook Graph API node, yes: n8n says you need a Meta for Developers account and a Meta app. Through Status 200 Uploads, no: our Meta app publishes for you.

Can n8n post to a Facebook group? No. Meta removed the Groups API, including publish_to_groups, from all versions on April 22, 2024. Page posts still work.

Can n8n post Facebook Reels? Yes. Send one video with postType reel. Facebook takes Reels of 3 to 90 seconds through us.

Is it free? Facebook and our n8n node are on every plan, Free included.

Sourced

All articles