An n8n social media scheduler takes a queue of social posts and gives each one a posting time. Mine does one more thing: it weaves post types together. It runs every 30 minutes, walks each account’s posting times in order, and fills each one with a post that isn’t the same type as its neighbors. So a promo never lands next to another promo, and a day of blog posts gets clips and deals mixed in. A generator below builds yours.
This post contains affiliate links. If you sign up through one, I earn a commission at no extra cost to you. I only point to tools I actually use or would recommend.
Batches of things lumped together
I write social posts in batches. A new blog post turns into a handful of social posts at once, a product push lands a set of promos, and a round of video clips shows up together. That’s efficient on my end. On a feed, it looks like a bot.
Before the scheduler learned to weave, that’s exactly what went out: a ton of blog posts in a row, when I wanted a promo and clips in between. I wrote about an earlier version in how I turn blog posts into social media posts, including the day it ran out of one blog and dumped 21 posts from another back to back.
Spacing out the blogs is only half of it, because I post more than one kind of thing. Without weaving by type, I’d have lots of the same kind of post going out back to back. Like PROMO, PROMO, PROMO. I don’t want that.
What does an n8n social media scheduler do?
It turns “these posts are ready” into “this post goes out Tuesday at 2:07 on this account.” Mine is one n8n workflow on a schedule trigger that runs twice an hour. Each run does the same five things:
- Reads my posting times, my spacing rules, my active accounts, the drafts waiting for a time and everything already scheduled, all from Airtable.
- Freezes anything going out in the next 48 hours, anything I’ve marked Locked and anything already sent. Frozen posts never move, but they still count as neighbors.
- Walks each account’s open posting times in order and picks a post for each one that passes the weave rules.
- Gives each post a small offset of up to 14 minutes, so nothing fires exactly on the hour.
- Writes the new times back to Airtable, only for the posts whose time changed.
Every post has a type, and the weave is built on those types. Mine are Blog, Clips, Deal, Tool, Promo, Quote, Meme, Affirmation and Other. A promo is a post about one of my own products.
The rules, all in one Code node:
| Rule | What it stops | My setting |
|---|---|---|
| Same type never touches | A promo right after a promo, a clip right after a clip | Blog posts are the only type allowed to pair up |
| No runs from one blog | Five posts in a row from the same blog | No three in a row. Pairs are fine when one blog is over half an account’s queue |
| Promo cadence | A page full of “buy my thing” | 1 promo per account per day, never on two days in a row |
| Same link gap | One blog post showing up twice in a week | Set per platform. The one behind my clumps was 7 days |
| Freeze window | Posts jumping around right before they go out | 48 hours |
The promo row came straight from me. The first time promos went into the mix, two landed on X the same Monday morning, so I asked for one promo every two days if possible. That’s the rule now.
Who is an n8n social media scheduler for?
It’s for you if you post to several social accounts, from more than one blog or with a mix of post types, and you already use Airtable and n8n or are willing to. Deals, promos, quotes, clips and blog posts all in one queue is exactly where clumps happen.
Skip it, or go smaller, if this sounds like you:
- You have one blog and post a few times a week. Put them in by hand, or let your publishing tool’s built-in queue handle it. There isn’t enough in the queue to clump.
- Every post you share is the same kind. If it’s all blog posts from one blog, there’s nothing to weave.
- You don’t want a database. The scheduler reads everything from tables. Without them, it has nothing to walk.
What do you need to build an n8n social media scheduler?
- n8n, cloud or self-hosted. Mine is self-hosted on a Hostinger VPS. Cloud is a monthly plan, self-hosted costs you the server.
- Airtable, free plan to start. It holds the queue, the posting times, the rules and the accounts. Any database n8n can read and write works.
- Something to publish the posts. I use Blotato, run by a separate n8n workflow that sends anything whose time has come. The scheduler only picks times. It never posts.
- Gmail or any email node, for the daily check below.
How does an n8n social media scheduler work?
The trick is walking the posting times, not the posts. My older version went post by post: take the next post, find it a spot, move on. When a post didn’t fit, it jumped ahead a bunch of slots, and whatever came next in line filled the hole it left. That’s how the clumps got left behind.
Now it goes slot by slot. For each open posting time, it looks for a post that fits there. A post that doesn’t fit just waits for the next time. When I tested that change on the live queue, the longest run of posts from one blog on one of my Facebook pages went from 5 to 2.
Two more fixes went in with it:
- Versions of one post get spaced out. A blog post turns into two to four social posts, and they were all written the same day, so they sat next to each other in line. The 7-day link rule then blocked each one for a week. Now they’re spread through the queue from the start.
- Types get their fair share of the week. Instead of grabbing whichever post has been waiting longest, it favors the type that’s furthest behind. That keeps the blog posts I wrote first from hogging the start of every week.
The daily check that tells me it’s still working
Once it worked, my next question was how I’d know it stayed that way. So there’s a second workflow, the Weave Check. Every morning at 7:30 it reads the next 60 days for every account, in time order, the way I’d scroll the calendar. It checks for runs of one blog, same-type neighbors and links that repeat too soon.
It only emails me when something’s off, plus an all-clear on Mondays. So a quiet inbox means it ran and found nothing. It never touches a row.
It has caught stuff, mostly batches of things lumped together. A few days after it went live, it emailed me about one of my Facebook pages with 7 tool posts back to back. The scheduler was comparing each open slot against posts way off in the future, past its 60-day window, where a run of tool posts was already frozen. Every tool post got refused until they all piled up at the end. Now it only looks at the next post if it’s within 36 hours. Without the check, I’d have found that by scrolling my own page.
Pinterest is left out of the weave and the check. Its queue runs months deep and pins never get re-planned, so it keeps its own simpler logic.
Get the generator
The generator asks what kinds of posts you share and how many of each a week, where they come from, which accounts get them and what your spacing rules are. It shows you a week in the order you’d write the posts, then the same week woven by your rules, so you can see the clumps disappear before you build a thing.
Then it writes you a prompt you can paste into Claude or ChatGPT to walk you through the whole build, a skill for Claude Code, or both. Every version keeps the parts I’d hate to lose: walking slots instead of posts, the freeze window, the daily check and a dry run before anything new gets added.
What it doesn’t do
It doesn’t write the posts or send them. Other workflows do those jobs, and this one only picks times.
It doesn’t know what’s in a post. If I tag a promo as a blog post, it gets woven as a blog post. My own products are the exception: a post linking to one of my product sites gets treated as a promo even if it was tagged wrong.
It doesn’t always find a perfect week. When one blog is more than half of an account’s queue, two in a row from it is the best it can do.
And it’s fragile. It took a long time to get it how I want it, and every time I add something new to the mix, something breaks. Right now it’s great, but I’m nervous to add anything else in. That’s why the generator bakes in a dry run: before a new type, blog or account goes live, run the scheduler without writing anything and check the result first.
Frequently asked questions
Can n8n schedule social media posts?
Yes. A schedule trigger runs a workflow every 30 minutes that reads your queue and gives each post a time, and a second workflow sends posts when their time comes. n8n doesn’t have a built-in social calendar, so the queue and the posting times live in a database like Airtable.
How do I stop scheduled posts from going out back to back?
Give every post a type, then fill your posting times one at a time and skip any post whose type matches the one right before it. A post that doesn’t fit waits for the next time. Filling slots in order, instead of placing posts in the order you wrote them, is what keeps batches from clumping.
How often should a brand post promos on social media?
I cap my own at one promo per account per day, and never two days in a row. That’s my rule, not an industry number. It came from two promos landing on the same morning and looking like a sales page.
How do I know my social media scheduler is still working?
Run a separate read-only check every morning that reads the upcoming posts in time order and looks for clumps. Have it email you only when something’s wrong, plus a weekly all-clear, so silence means it ran and found nothing.
Do I need Airtable for an n8n social media scheduler?
No. You need a table n8n can read and write, with each post’s account, type, link, status and scheduled time. I use Airtable. Google Sheets or n8n’s own data tables can hold the same fields.
Try it yourself
An n8n social media scheduler that weaves post types fills each posting time with a post that doesn’t match its neighbors, caps promos, and freezes anything about to go out. A daily check then tells you if a clump sneaks back in.
Start with the generator above, build the queue first, and run the scheduler as a dry run before it writes a single time. Once it’s live, point it at an n8n error workflow so a failed run doesn’t go unnoticed.
A tool I built
Build a Bio
Build a branded link in bio page in about a minute, then embed it on your own blog so your clicks land on your site, not someone else’s.
Build your bio →I run an affiliate program on the tools I build. Approved affiliates earn 20% on what their referrals pay, for up to a year. US only for now. See the program →
Related reading
- How I Turn Blog Posts Into Social Media Posts Automatically
- n8n Error Workflow: How I Stop Finding Out Days Later
- n8n Schedule Trigger Not Working? Mine Never Ran for 7 Weeks
- How I Make Multiple Pins From One Blog Post
Subscribe if you haven’t already. There are plenty more builds I haven’t written up yet. Go forth and automate the boring stuff.
