Planning against last month is the part that gets skipped
Weekly planning generally begins from scratch. The ideas the team had that morning fill the available slots, and a theme that had quietly gone silent six weeks earlier remains silent, because no one is keeping track of what is absent.
Absence is normally unseen. A calendar shows what is present. It takes a person to remember what was in the two previous months, and that kind of mental effort is something no one should have to do every week.
Performance belongs in the same view. Not to chase whatever spiked (that produces a calendar of imitations), but to avoid repeating a format that stopped landing.
This flow must not write into the calendar unasked. A proposal a person accepts in one click is useful. A calendar that fills itself is one people stop trusting.
How the ActionFlow runs on the canvas
Last month's output is the input. A Start Scheduled node runs weekly. A Notion node reads published items and existing calendar entries. An HTTP Request node pulls their performance data.
A Generate Object node returns a proposal with one item for each slot. Each item has a theme, a format, and the reason for its selection: theme balance, a gap, or a format that performed.
Returning reasons per slot makes the proposal reviewable in under a minute. A list of topics is a decision you must redo. A list with reasons is a decision you can check.
A Slack node in the Human in the Loop category posts the proposal for a single confirmation. No text is generated until someone accepts it.
When a submission is accepted, a Notion or Google Sheets node records the entries in the content calendar, and a Google Sheets node records the proposed themes so the balance calculation has a history to work from.
A Filter node removes slots that are already filled before the proposal is generated, so the flow never suggests replacing something that is deliberately scheduled.
Nodes this ActionFlow uses
- Start Scheduled: runs weekly before planning.
- Notion (Integration): reads published items and the current calendar.
- HTTP Request (Util): retrieves the performance data for the published set.
- Filter (Data): removes already-filled slots, so nothing that is deliberately scheduled is overwritten.
- Generate Object (AI Core): returns one item for each slot, with theme, format, and reason.
- Slack (Human in the Loop): posts the proposal for a single confirmation.
- Google Sheets (Integration): writes accepted entries to the calendar. Notion does the same.
- Google Sheets (Integration): logs proposed themes so theme balance has a history.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.