Blog Draft Agent
Live demo
Watch it work before it's live
Tuesday 10:00 draft slot
It is Tuesday 10:00 and the next unwritten row on the calendar is a guide to cutting warehouse pick errors, aimed at operations managers at distributors of 20 to 200 people, with notes covering the three causes the team sees most often and one customer story the founder wrote up last month. The four most recent published posts were two product updates and two customer stories.
What you'll need
Set up in minutes
Connect WordPress
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Content calendar
The topics you want written, in the order you want them - for each one the angle, who it is for, the category it belongs in, the call to action, and any facts, numbers or customer details the post is allowed to state. The agent only writes what is here.
Voice guide
How your blog should read - person and tone, sentence and section length, how technical to get, the words and claims you never want to see, and one or two published posts you consider the standard.
Choose which agent runs it
NoClick's built-in models work out of the box — or bring Claude Code, Codex, and other coding agents on your own subscription.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
The brief
About this agent
The blog does not stall for lack of ideas, it stalls because nobody has two free hours to write the post. Twice a week this agent takes the next topic off your calendar, reads what you already published so it does not repeat itself, writes the whole thing in your voice, and leaves it in WordPress as a draft with a Slack line pointing at it. You edit and publish, or you do not, but there is always something waiting.
What people use it for
- A full draft, not an outline - Each run produces a titled post of 600 to 1200 words with an opening, a body and the call to action your calendar asks for. Editing something real takes twenty minutes, which is the difference between a blog that ships and one that does not.
- It never repeats a topic - Before writing it reads your recent posts and skips anything already covered, then tells you which topic it moved past and why. Nobody has to remember what a guest writer published last month.
- No invented statistics - It can only state a number, a study or a customer result if your calendar notes contain it. Where a statistic would help and there is none, it describes the effect in words, so nothing goes out that you would have to defend later.
- Nothing publishes without you - Drafts only, every time, and existing posts are never edited. Publishing stays a decision a person makes after reading the draft, which is what makes it safe to leave running.
Before you fork
What do I need to set up?
A WordPress credential that can create posts and read your posts and categories, and a Slack channel for the draft links. The real work is the two variables: your content calendar with the notes each topic is allowed to use, and a voice guide describing how your blog reads. Both are plain English, and the staged runs in Setup let you read a draft before the schedule ever fires.
Could it publish something by accident?
Its instructions say draft only, never publish and never schedule, and it has no tool to edit or delete an existing post. If you want that enforced by WordPress rather than by instructions, connect it with a Contributor level account, which cannot publish at all, and your editors keep the publish button.
What does it cost to run, and can I change the schedule?
The schedule step controls the days and time, and it is set to twice a week out of the box, so about eight runs a month. A run that writes 1200 words costs more than a short chat reply but far less than an hour of anyone's time. Moving it to daily simply multiplies that, and a run that finds nothing safe to write costs almost nothing because it stops early.
Keep exploring
More ways to run it
Run it with your coding agent
More agents like this
GitHub PR Review Agent
Reads every pull request the minute it opens and leaves one comment with a plain read of the change, a verdict on each…
Stripe Checkout Recovery Agent
Catches every abandoned Stripe checkout and leaves a short recovery email in Gmail naming the exact items and prices the…
Stripe Revenue Digest Agent
Turns yesterday's Stripe activity into one Slack message every morning: what came in, what failed, who churned, and the one…
Failed Payment Recovery Agent
Turns every failed charge into a ready-to-send dunning email in Gmail and one Slack line, with the amounts and dates pulled…
Make it yours
Put Blog Draft Agent to work.
Free to start. Guided setup, a test run against staged conversations, and it's live.