Recipe · Creators
Channel session check
Opens each of this profile's rows in the Channels dataset and records whether the session is still signed in, signed out, or showing something that wants a person. The page patterns are generic English starting points — expect to add your own wording once for each platform you actually run.
On this page
What it does
Opens this profile's channel rows and records which sessions are still signed in — and which page is asking for a person.
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 navigates, so give it a profile whose session you are happy to have in use.
The 9 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 this profile's channelsLoad Channels into rowsevaluateStamp the sweepRun scriptloopEach channelLoop forEachEach time
setVarStart this row as uncheckedSet verdictgotoOpen the channelGo to {{loop.item.url}}on failure: continuewaitWaitevaluateRead the pageRun scripton failure: continuesaveRowsWrite the verdict backSave to Channelson failure: continuescreenshotScreenshoton 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.
Channels
readswritesThe register: one row per channel, which profile it lives in, and whether its session is still signed in.
- label
- Channel · text
- url
- URL · url
- platform
- Platform · select · Long-form video | Photo | Short-form video | Text and links | Other
- profile
- Profile · profile
- status
- Status · select · Unchecked | Signed in | Signed out | Needs attention | Row incomplete | Retired
- checked_at
- Checked at · datetime
- 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 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
Queue review
Marks every queued post whose publish slot passed while it was still only scheduled. Opens no page.
One profile · Opens no page · The Content queue 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