The flow
Starts it 1Logic 5Service 7
The steps in the order they run, from what starts it.
- 1When any workflow failsError triggerStarts it
- 2Optional: email instead of SlackGmailService
- 3Optional: open an incident page in NotionNotionService
- 4Read the error and fingerprint itCodeLogic
- 5Read what has failed beforeGoogle SheetsService
- 6New, repeating, or a storm?CodeLogic
- 7Is this worth telling anyone?IfLogic
- 8Always write it to the logGoogle SheetsService
- 9Route by severitySwitchLogic
- 10Repeat - logged, nobody wokenNo OpLogic
- 11Wake someone about credentialsSlackService
- 12Queue the input problemsGoogle SheetsService
- 13Send the rest to your endpointHttp RequestService
How it's built
- Starts on
- An event in a connected app
- Steps
- 13, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- Gmail, Google Sheets, Notion, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail, Google Sheets, Notion and Slack accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
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?
Plan an afternoon. 13 steps is enough that you should read each one before running it.
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 13 steps before you point it at anything that matters.