Nội dung
n8n auto-posting to Facebook uses an n8n workflow to call Meta’s official Facebook Graph API and publish content to a Fanpage on schedule without manual work. Shop owners and SMEs only need a long-lived Page Access Token, a workflow built with HTTP Request and Schedule Trigger nodes, and the system will post consistently on its own.
Key points
- You need a Fanpage where you are an administrator, a Facebook for Developers App with the permissions pages_manage_posts, pages_read_engagement, pages_show_list, and a long-lived Page Access Token.
- Posting is done through an HTTP Request node sending POST to /{page-id}/feed (use /photos for image posts); store the token in encrypted Credentials, and never hardcode it or expose it publicly.
- Use a Schedule Trigger with a Cron expression (for example 0 8,20 * * * for 8 a.m. and 8 p.m.) and set the timezone to Asia/Ho_Chi_Minh to post at the right peak hours.
- Keep a list of captions in Google Sheets so n8n can read the due row and post it, letting you plan a full week of content in one sitting.
- Follow Meta’s policies: only post to Fanpages you own, avoid overly frequent posting, respect API rate limits, and secure your token to avoid being locked out.
Using n8n auto-posting to Facebook is a way for shop owners and SMEs to save hours every week: instead of waiting for the right time and copy-pasting manually, you set up a background workflow that publishes content to your Fanpage on schedule. n8n is an open-source automation platform that connects to Facebook through Meta’s official Graph API, so you stay in control and do not depend on expensive intermediary tools. This article walks you through everything from preparing access rights and building the workflow to setting posting schedules and important policy notes to keep your account from being locked.
n8n and Facebook Graph API: what to prepare before you start
Before building the workflow, you need to understand the mechanism: n8n does not post “secretly” but calls the Facebook Graph API — the official API Meta provides to developers. Every post to a Fanpage must go through a valid Page Access Token. If you are not familiar with the platform yet, read what n8n is and how to install n8n to set up a stable environment (self-hosted or n8n Cloud).
What you need to prepare:
- A Fanpage where you are an administrator (it does not work with personal profiles — Meta has stopped allowing automatic posting to personal profiles).
- An App created in Facebook for Developers, with Pages-related permissions enabled.
- Permissions:
pages_manage_posts,pages_read_engagement, andpages_show_listaccording to Meta’s Pages API documentation. - A Page Access Token with long-term validity — obtained through Graph API Explorer and then exchanged for a long-lived token.
Note: to use real posting permissions for multiple people, the app usually has to go through Meta’s App Review. During testing on your own Fanpage (with admin/developer roles), the token still works without approval — a practical way for SMEs to get started.
Get a Page Access Token the right way
The token is the “key” that lets n8n post on your behalf, so make sure you obtain it through the proper process and secure it carefully:
- Go to Graph API Explorer in Facebook for Developers tools, and select the App you just created.
- Grant the permissions
pages_manage_posts,pages_read_engagement,pages_show_list, then create a User Access Token. - Call the
/me/accountsendpoint to get the Page Access Token for your Fanpage. - Exchange it for a long-lived token following the Long-Lived Access Tokens guide so it does not expire after a few hours.
Never paste the token into public content, screenshots, or shared files. In n8n, store the token in encrypted Credentials, not hardcoded directly in the node.
Build an n8n workflow to auto-post to Facebook
There are two common ways to call the Graph API in n8n. The first is to use the built-in Facebook Graph API node (see the node documentation on docs.n8n.io). The second is to use the HTTP Request node to call the endpoint directly — more flexible when you need to attach images or links.
A basic text-post workflow includes these steps:
- Trigger: choose the activation source — manual for testing, or Schedule Trigger to run on a schedule.
- Prepare content: use a Set node (or pull data from Google Sheets, RSS, a database) to prepare the
messagefield. - Call the Graph API: an HTTP Request node sends
POSTtohttps://graph.facebook.com/v21.0/{page-id}/feedwith themessageandaccess_tokenparameters. - Check the response: Facebook returns the post
idif successful; add an IF node to handle errors.
If you want to post with images, call the /{page-id}/photos endpoint with the url parameter (image URL) instead of /feed. To post with a link and preview, put the URL in the message field or use the link parameter. You can upgrade the workflow with AI to generate captions automatically — see how to connect n8n with ChatGPT to create content automatically before sending it to the Fanpage.
Schedule automatic posting at peak hours
The real power of automation is posting at the right time without human involvement. In n8n, replace the manual trigger with Schedule Trigger (see the Schedule Trigger documentation). You can set it by:
- Fixed intervals: every few hours, every day.
- Cron expression: for example
0 8,20 * * *to post at 8 a.m. and 8 p.m. — two time slots with strong engagement among Vietnamese users.
Practical tip for shop owners: keep a list of posts in Google Sheets (one caption + planned date per row), then let n8n read the due row and post it. This lets you plan a full week of content in one sitting, after which the system will post consistently on its own. When you want to expand to more channels and content types, see more ideas in n8n automation marketing.
Don’t forget to set n8n to the correct timezone (Asia/Ho_Chi_Minh) in the configuration, or the Cron schedule will run at the wrong time.
Meta policy notes to avoid being locked out
Valid automation is automation that respects Meta’s rules. To keep your account and Fanpage safe, follow Meta Platform Terms and community guidelines:
- Only post to Fanpages you own, and do not abuse the API to spam or post on behalf of others without permission.
- Avoid overly frequent posting: posting in bursts or repeating the same content continuously can easily be flagged by Meta as spam. Keep a natural pace, with a few quality posts per day.
- Respect API limits (rate limit): if you call too often, the Graph API will return temporary errors — add retry handling with delays in the workflow.
- Do not create misleading content, copyright violations, or excessive clickbait; AI-generated content still needs your review before publishing.
- Secure the token: if you suspect it has been exposed, revoke it and create a new one immediately in the App settings.
When you operate correctly, automation is not only safe but also helps your Fanpage stay active and look more professional. To learn more about AI and automation for marketing, see the AI guide section.
Frequently asked questions
Is n8n free for auto-posting to Facebook?
The self-hosted version of n8n (running on your own server) is free under the fair-code license; you only pay for the server. n8n Cloud is paid by plan. Facebook Graph API also does not charge for basic posting actions.
Do I need to know programming?
Not necessarily. n8n uses a visual drag-and-drop interface; you only need to get familiar with configuring the HTTP Request node and pasting the correct endpoint and parameters from the documentation. The hardest part is usually getting the Page Access Token, and this article has walked you through it step by step.
Can I auto-post to a personal Facebook profile?
No. Meta stopped supporting automatic posting via API to personal profiles many versions ago. You can only automate posting to a Fanpage (Page) that you manage.
What if my token keeps expiring?
Switch to a long-lived Page Access Token according to Meta’s documentation. Long-lived Page tokens usually do not expire as long as the app and permissions remain valid, but you should still check them periodically and have a process to recreate them when needed.
How many posts per day is safe?
There is no fixed number, but the rule is to prioritize quality and a natural posting rhythm. For SMEs, 1–3 valuable posts per day is often more effective and safer than spamming dozens of duplicate posts.
