Build a Self-Filling Content Calendar with n8n

Most content calendars die the same way: the planning sheet looks great in January, then a busy week leaves three empty slots, then a busier week leaves ten, and by March nobody trusts it. The fix isn't more discipline. It's a workflow that notices the empty slots and fills them with drafts before anyone has to. An n8n content calendar automation does that, it reads the plan, finds the gaps, and drafts only what's missing.

The templates ranking for this generate pillars and posts in one shot and store them. Useful once. But they don't detect which slots are still empty next week, don't fill gaps on a recurring basis, and don't gate anything for review. This build adds the three pieces that turn a one-time generator into a calendar that maintains itself.

What a self-filling calendar handles

The calendar isn't just a list of dates. It runs the planning loop:

• Content pillars weighted by how often each should appear
• A two-week or month-out grid of planned slots
• Gap detection that flags slots with no content yet
• AI drafts generated only for the empty slots
• A review status on every generated draft
• A log of what shipped, feeding next cycle's balance

Plan around the channels you publish on. A calendar full of slots for a platform you've abandoned just generates waste.

The content calendar pipeline

Schedule trigger → Read calendar → Detect gaps → Draft for empty slots
       → Parse → Write back as draft → Review gate → Log shipped

A Schedule trigger wakes the workflow. It reads the upcoming slots, finds the empty ones, drafts posts for only those, writes them back as review-ready drafts, and logs what eventually ships so the pillar balance stays honest.

1. Model the calendar in a sheet

Keep the calendar as a Google Sheet, one row per slot: date, pillar, channel, status, content. The status column does the heavy lifting, planned, drafted, approved, shipped. Everything downstream reads and writes that field. A sheet beats a fancy database here because the team can eyeball and edit it directly.

2. Read the upcoming window on a schedule

A Schedule trigger fires, say, every Monday, and reads the next two weeks of slots. Keep the window short and the interval sane. A Schedule trigger set to fire every minute will silently drop runs when the previous execution is still in flight, so a weekly or daily cadence with a real interval is the safe choice for a planning loop.

3. Detect the gaps

This is the step the popular templates skip. Filter the upcoming slots to those where status is still planned and content is empty. Those are your gaps. The workflow generates for those rows only, not the whole window, so a re-run doesn't regenerate posts that are already drafted or approved.

4. Draft for the empty slots

For each gap, run an OpenAI prompt seeded with that slot's pillar and channel, so the draft matches the plan. Parse the response into clean fields with a Code node before writing it back, the model returns text and the Sheet update expects specific columns. Write the draft into the content column and flip status to drafted.

5. Gate, then log what ships

Drafted is not approved. Notify an editor that new drafts are waiting, and let them set status to approved (or edit and approve). A separate publishing workflow picks up approved rows on their date. When a post ships, log it, that record feeds the next cycle's pillar weighting so an over-used pillar naturally gets fewer new slots.

Implementation patterns worth copying

Pattern: weight the pillars

Don't let one pillar eat the calendar. Store a target share per pillar, and when generating gaps, bias new slots toward under-represented pillars based on what actually shipped. The Social Media Scheduler & Designer logs everything to a Sheet for exactly this kind of calendar bookkeeping, the shipped log is what keeps the mix balanced.

Pattern: draft a buffer, never just-in-time

Generate two weeks ahead, not the morning of. A buffer means a failed OpenAI call or a sick editor doesn't leave a hole in tomorrow's schedule. The gap-detection filter already supports this, just widen the read window and the buffer fills itself.

Pattern: keep humans on approval, machines on drafting

The split that works: the workflow owns drafting and gap-finding, a person owns approval. That's where the time goes back into the day without handing the brand voice to a model. Auto-approve only the lowest-stakes recurring slots, if any.

A note on what the calendar should not try to do. It's tempting to wire posting analytics back in and let the model retune the cadence on its own. Resist that on day one. A feedback loop that changes the plan based on last week's engagement sounds smart and, in practice, chases noise, one viral post skews the weights and the calendar lurches. Log the performance data, look at it monthly, and adjust the pillar weights by hand until you genuinely trust the signal. The boring version ships content reliably; the clever version tends to ship surprises.

n8n nodes you'll use most

Getting started

1. Build the calendar sheet: date, pillar, channel, status, content.
2. Define pillar weights so the mix stays balanced over time.
3. Add a Schedule trigger that reads the next two weeks of slots.
4. Filter to slots that are still planned with empty content, those are the gaps.
5. Draft only the gaps with OpenAI, parse, and write back as drafted.
6. Notify an editor and let approval flip the status by hand.
7. Log shipped posts so the next cycle rebalances the pillars.

To fill the slots from real source material, build an n8n content repurposing workflow turns one source into many channel posts, and turn a podcast into a blog post with n8n feeds episode-derived drafts straight into open calendar slots. When the queue needs a distribution layer, the Content Scheduler & Distributor reads it and formats per channel.