The flow
Starts it 3Logic 15Service 7
The steps in the order they run, from what starts it.
- 1Every 5 minutesSchedule triggerStarts it
- 2Run once nowManual triggerStarts it
- 3Every morning at 08:00Schedule triggerStarts it
- 4Endpoints to watchCodeLogic
- 5Read what happenedCodeLogic
- 6Split endpointsSplit In BatchesLogic
- 7Build digestCodeLogic
- 8Ping endpointHttp RequestService
- 9Anything worth sending?IfLogic
- 10Judge responseCodeLogic
- 11Send daily digestSlackService
- 12Quiet day, say nothingNo OpLogic
- 13Healthy?IfLogic
- 14Track state changeCodeLogic
- 15Wait 30 secondsWaitLogic
- 16What happened?SwitchLogic
- 17Still down long enough to escalate?IfLogic
- 18Second attemptHttp RequestService
- 19Compose down messageSetLogic
- 20Compose recovery messageSetLogic
- 21Escalate to on-callSlackService
- 22Confirm outageCodeLogic
- 23Alert: went downSlackService
- 24Append to outage logGoogle SheetsService
- 25Alert: recoveredSlackService
How it's built
- Starts on
- A clock
- Steps
- 25, with 4 branches, 2 loops or waits
- Size
- Large: read it before trusting it with anything live
- Connects to
- Google Sheets, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Sheets and Slack accounts. 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 25 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 25 steps before you point it at anything that matters.