What this agent does
A content calendar only works if drafting keeps pace with planning — otherwise "Ready" ideas sit for days waiting for someone to actually write the caption. This agent watches your Notion content database and the moment an idea is marked "Ready", it drafts three caption variants and attaches them to the same row.
stage-1-poll— polls your content calendar database for rows that changed to a "Ready" status since the last check.stage-2-caption-draft— for each newly-ready row, reads the idea/brief field and writes 3 distinct caption variants (different hooks, same core message), then writes them back into the row's variant fields.
Every run logs which rows were processed, so re-runs never double-draft the same idea.
Requirements
- A Notion content calendar database with a status field (e.g.
Idea,Ready,Posted) and a text field for the brief/idea. - Notion API integration token with access to the database (see the included install guide).
- Works on OpenClaw (scheduled trigger + Notion plugin) for the recurring watch behavior.
Setup
- Unzip the package into your workspace, keeping the folder structure intact.
- Create a Notion integration, share your content database with it, and put the token in your
.env. - Map your actual property names (status field, brief field, variant fields) to what the pipeline expects.
- Run the starter prompt against one "Ready" row to confirm the mapping is correct.
- Schedule it to poll every 15-30 minutes.
What you get
- Notion rows automatically detected the moment they're marked "Ready", no manual polling
- Three distinct caption variants drafted per idea, with different hooks but the same core message
- Variants written straight back into the same row, ready to pick from
- A processed-row log so re-runs never double-draft the same idea
