Recipe · Creators
Queue review
Reads the Content queue and moves every post whose publish slot has passed while it was still only Scheduled to Needs review. Opens no page and posts nothing — a draft stays a draft and a published row is never re-judged.
On this page
What it does
Marks every queued post whose publish slot passed while it was still only scheduled. Opens no page.
It runs against one profile, through that profile's own proxy and with its own cookies — so the pages load the way that account's owner would see them. It opens no page at all, which means it can be run against a profile whose session you would rather not disturb.
The 5 steps
The real tree, read out of the pack the launcher ships. Indentation is nesting: the steps under a loop run once per row, and the ones under a branch run only when the condition above them holds. Every {{…}} is a value filled in at run time — from the row being walked, from a setting on the run, or from the profile itself.
loadRowsLoad the queueLoad Content queue into rowsevaluateRead the clock onceRun scriptloopEach queued postLoop forEachEach time
evaluateHas this slot passed?Run scriptsaveRowsFile the verdictSave to Content queueon failure: continueEach of those is one of the step types on the automation reference, with the same fields the editor shows and the same fields an agent is handed over the local API.
The tables it uses
These load with the recipe. A dataset is a typed table your workspace owns — the columns are named and typed up front so the steps can address them, and every one of them is yours to rename, extend or fill from a file afterwards.
Content queue
readswritesWhat is due to go out, on which channel, and when. The queue review flags anything whose slot has passed while it was still only scheduled.
- title
- Title · text
- channel
- Channel · text
- url
- URL · url
- publish_at
- Publish at · datetime
- profile
- Profile · profile
- status
- Status · select · Draft | Scheduled | Published | Needs review
- notes
- Notes · longText
Re-running updates the row it already wrote rather than adding a second one. That is what the match column in the save step is for, and it is the difference between a status check and a table that doubles in size every pass.
Loading it
In the launcher, open Automations, choose Load a starter pack, and pick Creators. Untick anything you do not want. The tables land first, then the workflows, then a project called Creator Ops that links them together.
What arrives is an ordinary automation row. Open it in the editor, change a step, rename it, delete it — nothing in the app treats it as special afterwards, and loading the pack a second time makes a fresh copy rather than overwriting the one you edited. Tables are the opposite: an existing table of the same name is reused and keeps its rows.
The rest of the creators pack
They load together, share the tables above, and land in one Creator Ops project.
Channel session check
Opens this profile's channel rows and records which sessions are still signed in — and which page is asking for a person.
One profile · Its own proxy and cookies · The Channels table
Channel register audit
Flags channel rows that are missing a label, a URL, a platform or a profile of their own. Opens no page.
One profile · Opens no page · The Channels table
Post metrics sweep
Reads a channel's own analytics page in this profile's session and files the per-post numbers.
One profile · Its own proxy and cookies · The Post metrics table · 3 settings on the run