Skip to content

Content calendar batch that waits for you to name the rows

On a schedule it writes a week or month of dated posts into a plain calendar file, checked against recent topics so it does not repeat. Drafting and approval are separate steps. A post goes out only after you name its row number in a live reply, and anything over two weeks old is marked stale.

MarketingWorks with Claude Code · n8n+1Community example
Build your promptSee requirements

What it does

  • Batch writes dated, platform tagged posts in your brand voice
  • Checks the calendar so it does not repeat a recent topic
  • Queues each row as drafted or ready for approval, never approved
  • Lists ready rows as a numbered batch with the final text and destination
  • Flags rows older than fourteen days as stale

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Publishing any post, which needs you to name the row numbers in a reply
  • Sending any cold email

You decide what happens next.

More about this workflow

This setup is for marketers and solo creators who need steady output without losing their voice. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it batch writes dated, platform tagged posts in your brand voice. Next, it checks the calendar so it does not repeat a recent topic. Then it queues each row as drafted or ready for approval, never approved. After that, it lists ready rows as a numbered batch with the final text and destination. Finally, it flags rows older than fourteen days as stale. It works with your social scheduler, automation platform and docs, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before publishing any post, which needs you to name the row numbers in a reply and sending any cold email, and says plainly if a step cannot be undone.

“generation and approval are always two different steps”
marcosmodly marcosmodly on GitHub · Sep 25, 2026
Before you startSocial scheduler · Automation platform accessScoped permissionsClaude Code or n8n
Explore required tools and model recommendations

Tools and access

  • Social scheduler

    Handles the social scheduler part of this job. Grant draft or queue access, not publish.

    API required: Optional. Use your current scheduling tool. Many have an API, or the agent can hand you drafts.

    No sign-up needed

  • n8n

    Handles the automation platform part of this job. Grant create workflows, left inactive until reviewed.

    API required: Yes. Needs an n8n API key from settings. New workflows should stay inactive until you review them.

    Sign up: n8n

  • Google Docs

    Handles the docs part of this job. Grant one folder, create and edit only.

    API required: Yes. Needs a Google Cloud OAuth app with the Docs API turned on.

    Sign up: Google Workspace

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

GPT-6.1 Sol

Strong general writer at a mid price.

$2 per million input tokens, $10 per million output tokens, for prompts up to 272K tokens. Longer prompts cost $4 in and $15 out.

OpenAI docs as of October 11, 2026

Cheaper backup

GPT-6 Luna

Very low cost for first drafts and digests.

$0.10 per million input tokens, $0.50 per million output tokens, for prompts up to 272K tokens.

OpenAI docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

week, month

2Your prompt

4 of 4 still empty
Fill these in before you run it: [BRAND VOICE FILE] [PLATFORMS AND ACCOUNTS] [CADENCE: week, month] [WEBHOOK OR SCHEDULER FOR APPROVED POSTS] You are the Content calendar batch that waits for you to name the rows agent. On a schedule it writes a week or month of dated posts into a plain calendar file, checked against recent topics so it does not repeat. Drafting and approval are separate steps. A post goes out only after you name its row number in a live reply, and anything over two weeks old is marked stale. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Batch writes dated, platform tagged posts in your brand voice - Checks the calendar so it does not repeat a recent topic - Queues each row as drafted or ready for approval, never approved - Lists ready rows as a numbered batch with the final text and destination - Flags rows older than fourteen days as stale What you must never do without a yes from a person: - Publishing any post, which needs you to name the row numbers in a reply - Sending any cold email Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, n8n, Make

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Set up Social scheduler. Keep it to draft or queue access, not publish.
  2. 2Connect n8n with its own login, not yours. Grant create workflows, left inactive until reviewed.
  3. 3Connect Google Docs with its own login, not yours. Grant one folder, create and edit only.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: publishing any post, which needs you to name the row numbers in a reply, sending any cold email.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 78.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Content calendar batch that waits for you to name the rows](https://trustcase.dev/badge/content-calendar-batch-that-waits-for-you-to-name-the-rows.svg)](https://trustcase.dev/use-cases/content-calendar-batch-that-waits-for-you-to-name-the-rows)
HTML
<a href="https://trustcase.dev/use-cases/content-calendar-batch-that-waits-for-you-to-name-the-rows"><img src="https://trustcase.dev/badge/content-calendar-batch-that-waits-for-you-to-name-the-rows.svg" alt="Trustcase trust score for Content calendar batch that waits for you to name the rows" height="20"></a>

More marketing workflows

  • Thursday newsletter draft that sends Sunday only if approved

    On Thursday the agent drafts Sunday's issue from the week's events and the last eight issues' results: subject, intro, up to three picks and at most one A/B test. You approve, edit, redraft or skip from your phone. Sunday sends only an approved draft, and a week with no approval is skipped with a note to you.

  • Community thread replies with promo rule checks and a daily cap

    Finds forum threads where people are asking for something your product does, ranks them by buying intent and drafts helpful replies. Each draft is checked against the community's self promotion rules, disclosure and spam signals. Posting is off by default and each reply needs your approval of the exact text, with a daily cap and cooldowns.

  • Content drafts that learn rules from your approval notes

    A small team of agents researches, drafts, fact checks and plans content for each of your brands from a brand file and real examples of your voice. When you approve a draft with a note, the note becomes a rule every agent reads first. It only writes drafts and nothing is published on its own.

  • Email campaign drafts with pre-send checks and a count matched yes

    Builds an email campaign as a draft in your email platform and runs automatic checks on links, tracking tags, fallbacks and the unsubscribe footer. It can only send or schedule when you type a phrase that includes the live recipient count.

Other workflows that use the same tools