Building a Social Media Automation System with n8n for Facebook Posting

  • ~75% less hands-on time per post
  • 2.5x more posts a month
  • 81% of generated drafts approved
  • ~2,100 workflow executions a month

A UK marketing agency used to spend nearly 50 hours each month manually posting to its clients' Facebook pages. We developed an n8n social media automation system which reads the content plan from Google Sheets, uses an AI agent to draft each post, sends it to an editor for one-click email approval, and then publishes it to the correct page on schedule, with a human review always being kept informed.

Laptop showing an automation canvas with five connected nodes — read the planning sheet, draft the post, validate it, send the approval email, publish — beside an execution log, and a phone with the approval email carrying the draft, the image and approve and request changes buttons

|  

Project Details

A UK-based digital marketing agency looks after Facebook pages for about 14 of its client brands, the brands ranging from a regional retail chain to a B2B SaaS company and one enterprise client in the logistics sector. Two content managers used to write, schedule, and publish each post manually, and the agency now wishes to automate this work using a self-hosted stack that it has control over, without abandoning the sign-off stage which its clients had agreed to in writing. Our custom AI solutions connect the tools a team already uses while preserving its approval rules and operational requirements.

CLIENT
Digital marketing agency (under NDA)
INDUSTRY
Marketing & Advertising
SOLUTION
Social media content automation with AI post generation and an email-based approval workflow
SERVICE
Workflow Automation + AI Integration + QA
PLATFORM
n8n, Facebook API, Google Sheets
SCOPE
3 n8n workflows, ~40 nodes, 14 Facebook pages
DURATION
6 weeks, plus ongoing support
LOCATION
UK

|  

Business Challenge: Automating Facebook Posting Without Losing Editorial Control

The agency had worked out its content strategy and set down a strategy for each account. The account managers would agree with each client on monthly themes and keep in a shared Google Sheet all the posts that were planned, including the brand, topic, angle, call to action, link and publish date. There were about 120 rows a month. It was the stuff that happened after a row had been entered that took up the time.

The content manager took the brief, composed the post, checked it to make sure it matched the client’s brand voice notes, pasted it into the Meta Business Suite, attached the image file, chose a time slot and then moved the entry to the ‘done’ column. It took between twenty and thirty minutes to produce each post and, between the two of them, they spent about 50 hours a month on tasks that always followed the same six steps. The entire point of the brief had been to save time on those steps, and the posts published on Monday morning were written on Friday afternoon, with the exception of when the client sent a late change, in which case someone had to locate the scheduled post and have to redo it by hand.

Clock icon

Manual Posting Slows Down Content Distribution

Each post was handled by one of two individuals, and if either of them was unavailable, activity would cease. In a normal month, approximately 9% of the scheduled slots were missed, and the agency could not accept a new client unless it first hired someone.

Warning icon

Keeping a Human Approval Step in an Automated Flow

Since client contracts had to be signed off before anything could go live, it wasn't possible to have a completely hands-off pipeline. The approval was still necessary, but only as a two-minute task in the inbox rather than requiring a login to yet another tool.

Exchange icon

Connecting Content Planning, Generation, and Publishing

Plans lived in Google Sheets, drafts in Docs, scheduling in Meta Business Suite, feedback in email threads. None of those systems talked to each other, so status data was tracked by hand, nobody could say which posts were waiting on whom, and the enterprise client's quarterly audit request took a full day to answer.

|  

Technologies Behind the n8n Social Media Automation Workflow

|  

Our n8n Social Media Automation Solution

One question shaped the build: what has to stay in human hands? Only the final read. Everything before it (pulling the brief, writing the draft, scheduling, the publish call) and everything after it (status write-back, reporting) could be automated with n8n workflows without changing how the planners worked.

What makes us choose n8n over a SaaS scheduler? The agency wanted the automation to be located on its own servers, using its own API keys and its own data, and the ability to modify the logic without having to wait for the vendor. By using a self-hosted instance of n8n within Docker, they achieved this at a lower monthly cost than the subscription that it replaced. Since our company is both an n8n automation agency and one that develops AI products, the same small team handled both the LLM aspect and the workflow aspect, keeping the stack simple: n8n, one LLM API, Google Sheets, SMTP, and the Facebook Graph API. Apart from the sheet, there was no database, and beyond one Code node containing 40 lines of code, there was no custom code.

There are three workflows, totaling around 40 nodes. The first one reads new data from the planning sheet on a schedule and passes each brief to an AI agent node, using that client’s brand voice guide as context. The second one sends the draft email to the appropriate editor, waits for a webhook, and then records the decision in the row. The third one publishes the approved posts via an HTTP Request node at the scheduled time and writes the post ID back. The page credentials are stored in n8n’s credential store, meaning access is managed in a single location and is never copied into the node parameters; the model, temperature, and length settings are all located in one Set node within the production workflow, so that a single change is applied to all of the 14 clients’ prompts. The instance has only three external connections: Sheets, SMTP, and Meta.

We configured AI agents for marketing to turn each client’s briefs and brand guidelines into drafts ready for editorial review. When the agent receives the brief, the brand voice document (outlining the tone, the banned words and the hashtag rules), the last five published posts, and the desired length, the output goes through a validation process consisting of checks on length, links, banned words, and a flag indicating whether the draft repeats a recent hook. If a draft fails any of these checks, it is sent back to the LLM node once, with the reason for the rejection included; in about 6% of cases, a second pass is needed. Each response is then assessed on a scale from 1 to 5 by a second, less expensive model call, and those rated below 3 are regenerated before being presented to a human.

01

Content Planning in Google Sheets

The only genuine source of truth remains the planning sheet which the agency has already been using, with twelve columns for each post, one row for each post, and a status column that is updated by the n8n workflows themselves: planned, drafted, awaiting approval, approved, published, failed. New data added to the sheet is detected within 30 minutes and the row data is never copied to any other place.

02

Automated Post Generation

The AI agent creates each post using the brief and the client's brand voice guide, after which it checks the post for length, links, and banned words. A draft is prepared about 20 seconds after the row is taken, and the token cost is around $0.03 per post, meaning that producing 300 posts a month costs less than one hour of a content manager's time. The quality has also been maintained across accounts in different niches, for example, with a cycling retailer and a legal services firm.

03

Email-Based Approval Workflow

The editor receives one email for each draft containing the text, the image, the target page, and two buttons: Approve and Request changes. The comment box on the change path sends the note directly back into the regeneration prompt. The median time taken for a decision is around 40 minutes; the human review remains necessary, although it is no longer the bottleneck.

04

Scheduled Publishing via the Facebook API

Approved posts are held in a queue and are sent out at the time specified in the sheet via the Graph API, with two retry attempts made if temporary errors occur; the post ID, the publish time, and any message from the API are then recorded in the row, so the sheet serves as a publication log and the publishing data is available to any team member who has access to the sheet.

05

Operations Digest and Alerts

A brief reporting workflow sends out a daily summary to the agency's Slack, including the number of drafts produced, the number of posts waiting for approval, those that have been published, and those that have failed. If a piece remains in the approval stage for more than 24 hours, a reminder is sent to the editor, and if a publication fails, the ops lead is informed. Each month's digest file is exported to a Drive folder, ensuring that the publication history is retained even if a record is deleted.

Planning a social media automation of your own?

Request similar solution

— Agile Development Methodology

|  

Project Journey

The project lasted six weeks and was carried out in three two-week sprints, involving a two-member LITSLINK team consisting of an automation engineer who developed the n8n workflows and another engineer who was in charge of QA, setting up the Facebook API, and onboarding each client page. After the first sprint had ended, the generation workflow was able to produce drafts for two pilot brands, and the agency’s editors then began reviewing actual output rather than mockups.

0
Week sprint cycles
0
Sprints completed
~40
Nodes across 3 workflows
0
Team members

|  

How the n8n Facebook Automation Workflow Works

1
Pull Content Briefs From Google Sheets
  • A schedule trigger fires every 30 minutes. The Google Sheets node reads rows marked "planned" with a publish date inside the next seven days and locks each one by setting its status to "drafted".
2
Generate the Post Draft
  • The brief, the brand voice guide, and recent posts go into the AI agent node. The output is checked for length, links, and banned words, then saved back to the row with a one-line note on the angle chosen.
3
Send the Draft for Email Approval
  • An email with the text, image preview, and two action links goes to the editor assigned to that brand. A Wait node holds the execution until the webhook fires with approve or request changes.
4
Publish the Approved Post to Facebook
  • At the planned time, an HTTP Request node calls the Graph API with the page token, creates the post, and writes the Facebook post ID back to the sheet. Errors retry twice, then alert.

|  

Scrum Process Flow

Every sprint ended with a demo against live client briefs. Sprint one proved generation on two pilot brands, sprint two moved approval and publishing into production with the agency’s editors in the loop, and sprint three brought the remaining twelve pages in and added reporting. Both teams shared one Slack channel, so most questions got a response the same hour. Workflow automation at this scale needs a working version in front of the people who will live with it, not a long roadmap.

Automation canvas with the whole chain: schedule trigger, read the planning sheet, draft the post against the brand guidelines, validate, send for approval, wait for the webhook, publish — with the monthly execution count, success rate and the latest runs listed beside it
Inside Each Sprint
Plan Design Develop Test Review
Daily Scrum
15-min sync every morning
Retrospective
Inspect & adapt process
Sprint Review
Demo to stakeholders
Increment
Shippable product update

|  

Delivery Process: How We Created the n8n Social Media Automation Solution

1
Scope & Timeline
  • We define the project goal together, agree on priority features, and set a realistic delivery date and budget.
2
Feature Priorities
  • We build a ranked list of everything the product needs, starting with what matters most to the business.
3
Sprint Kickoff
  • Work is broken into 2-week cycles. At the start of each, we select the next set of features to deliver.
4
Development Cycle
  • The team builds, tests, and integrates features throughout the sprint.
5
Review & Feedback
  • At the end of every sprint, you see working software and give feedback that shapes the next cycle.
6
Delivery
  • Each sprint produces a shippable piece of the product. We review what worked, adjust, and move forward.

|  

Workflow UX: Simple Interfaces for Content Creators and Approvers

Since no one at the agency was willing to learn a new tool, there isn’t an app. The content planners use the sheet they already have, which has four extra columns and includes a status column that updates automatically. The conditional formatting colors each row according to its status, so that a planner can open the sheet on a Monday and at a glance see the week’s status: green means it’s published, amber means it’s waiting on an editor, and red indicates it has failed and needs to be looked at.

The approval process is carried out via email. Each message includes a subject line indicating its content (for example, “Brand X, draft for Oct 14, 9:00 AM, approve?”), the body text set out as it will appear on the page, an image placed below it, and two big buttons. When ‘Request changes’ is selected, a short form opens up with a comment field, and the comment entered in this field is then passed on to the following generation word for word. Editors have told us that the one-line note stating the angle that the agent had chosen helped speed up the review process since they no longer had to reread the brief in order to assess the draft. For a related example of content generation with human approval, explore our AI product description generator case study, where merchants review and approve product copy before publication.

The n8n editor itself is opened only by the agency’s ops lead. From there, she can move the schedule, swap the model, raise the retry count, or connect a new Facebook page by adding one credential, without writing code. Every node carries a sticky note explaining what it does and which column it reads or writes, which is a small thing that has kept the workflows maintainable through three handovers. Nothing in the setup exists only in someone’s head, and the ops lead created the 15th page connection herself in week eight, with no help from us.

Phone showing the approval email: the subject naming the brand and the channel, the draft text with its hashtags, the image, the scheduled time and the target page, and approve and request changes buttons with a comment field
Content plan table for a month: each row carries the date, the client, the channel, the theme, the brief, a link to the draft, the status from planned to published or failed, the editor and the published post id, with status filters above
Phone showing the published post on the page with its text, hashtags and image, the reactions and comment count below, and a banner confirming it was published at the planned time by the workflow

|  

Results

Before

  • ✕~120 posts a month written and scheduled by hand, 20 to 30 minutes each
  • ✕~50 hours a month of content manager time spent on posting mechanics
  • ✕~9% of planned slots missed, mostly when someone was out of office
  • ✕Client sign-off chased over email threads, with no record of who approved what
  • ✕Plans, drafts, scheduling, and feedback split across four tools

After

  • ✔~300 posts a month from the same two-person team, 2.5x the previous volume, automated publishing on every page
  • ✔~6 minutes of human time per post, about 12 hours a month in total
  • ✔<1% missed slots, with retries and alerts covering API failures
  • ✔Every approval logged with editor, timestamp, and comment on the row
  • ✔One sheet, one inbox, one n8n instance, status visible at any time
Impact dashboard for the first quarter after launch: posts per month, hands-on time per post, share of drafts approved and missed slots as before-and-after figures, posts per month by client, and the daily digest of drafted, awaiting approval, published and failed items

Impact of the Social Media Automation

Start with the figures: the amount of hands-on time spent on each post fell from around 25 minutes to 6, and the number of posts produced each month increased from about 120 to 300, all without hiring any new staff, which enabled the agency to secure four new accounts in the first quarter following the launch without having to expand its content team. The running cost is under $40 per month for LLM tokens and hosting. The approval rate—the quality measure that the agency monitors—rose from 64% of drafts being approved without any changes in the first week to 81% by the end of the third month as the rejection comments were fed back into the prompts and the quality of the first drafts improved. The time it took to respond to a client's late change decreased from one day to about one hour.
The aspect that had not been included in the initial proposal was the audit trail, and its worth became apparent very quickly. Previously, disagreements over 'we never approved that' had cost the agency an hour or two each month and, on one occasion, a client; these disputes have now ceased because each row includes the name of the approver, the timestamp, and a comment, and the agency presents this log to potential customers as part of its sales pitch, a feature that very few marketing workflows can provide. The aim had been to save time; the business advantage that the client mentions most frequently is the ability to prove exactly what was sent out, when, and on what basis. For the enterprise account, the log is now included in the contract. Marketing teams that wish to increase their output generally believe that the AI is the difficult part; in this case, it was the handoff, and the essential point was to keep the human element involved.
Faster Publishing
Editorial Control Kept
Scaled Without Hiring

Want the same workflow running for your pages?

Contact us

|  

What's Next

Teams that need help with further AI integrations and ongoing model maintenance can explore our AI as a Service offering. Facebook was the test case, and the content strategy for each brand is already set out in the sheet; the same sheet, the same approval email, and the same n8n workflows can be used for the other platforms by adding one formatting step for each channel:

  • Multi-Platform Expansion (Instagram, LinkedIn, X): Instagram comes first because it shares the Graph API and the page credentials already in the instance. LinkedIn and X each need their own API keys, their own app integrations, and a character-limit branch, and both are scoped for the next quarter.
  • Comment Monitoring With Sentiment Analysis: A workflow that pulls comments on published posts every hour, runs sentiment analysis, and routes anything negative to the account manager before it sits unanswered overnight.
  • Performance Loop: Reach and engagement data pulled back into the sheet per post, so the agent can see which hooks perform for which brand and stop guessing. Early tests on two accounts are running now, with engagement data landing in the sheet as a new column.
  • Image Generation: Adapting one hero image into per-platform sizes, then generating simple visuals for posts that arrive without one.
Channel preview of one post rendered for four social platforms with their character counts, and a comment monitoring panel below grouping incoming comments as positive, neutral or negative with a route to account manager action

— Verified Reviews

Our Reputation on Top Platforms

LITSLINK has a 4.8 rating on the major platforms, and clients who have written about our AI integration and automation services most frequently highlight on-time delivery, clear communication during the short engagements, and a readiness to challenge requirements when a simpler workflow would suffice.

Clutch B2B Ratings & Reviews

4.8

78 reviews

Top Developer
GoodFirms Research & Reviews Platform

4.8

32 reviews

Top Company
Behance Creative Portfolio Platform

150+

design projects

View projects

Have an n8n Automation Project in Mind?

If you want an n8n social media automation system for your agency or a workflow that links the tools your team currently uses and keeps your data on your own servers, let us know what you post, where it is approved, and how many pages you operate, and our specialist will reply to you within 48 hours with a scope and a price.

Next steps:
1
LITSLINK specialist reviews your request and contacts you to discuss the details;
2
If needed, we can sign an NDA before moving forward;
3
We send a project proposal – estimates, timeline, and team CVs included;
4
After launch, we stay on for any updates your product needs.
⚡ 48h Response
💙 1540+ Projects