The flow
Starts it 1Logic 14Service 7
The steps in the order they run, from what starts it.
- 1Check Every HourSchedule triggerStarts it
- 2Watchdog SettingsSetLogic
- 3Read The Watch ListData TableService
- 4Check Each Watched WorkflowSplit In BatchesLogic
- 5Read The Ledger OnceLimitLogic
- 6Get The Last Successful RunN8nService
- 7Read The Ledger BackData TableService
- 8Did It Run At All?IfLogic
- 9Note The n8n API Read FailedSetLogic
- 10Summarise This SweepCodeLogic
- 11Read What That Run ProducedN8nService
- 12Treat A Never-Run Workflow As DarkSetLogic
- 13Decide The VerdictCodeLogic
- 14Did The Sweep Have Blind Spots?IfLogic
- 15Count What The Run ProducedCodeLogic
- 16Record The VerdictData TableService
- 17Report The Blind Spots To SlackSlackService
- 18Nothing To ReportNo OpLogic
- 19Worth Waking Someone?IfLogic
- 20Post The Alert To SlackSlackService
- 21Stay QuietNo OpLogic
- 22Close The LoopNo OpLogic
How it's built
- Starts on
- A clock
- Steps
- 22, with 3 branches, 1 loop or waits
- Size
- Large: read it before trusting it with anything live
- Connects to
- Slack, n8n data table
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Take your time. At 22 steps it is large: read it before trusting it with anything live.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 22 steps before you point it at anything that matters.