The flow
Starts it 2Logic 12Service 7
The steps in the order they run, from what starts it.
- 1When Workflow Error OccursError triggerStarts it
- 2When Daily Digest StartsSchedule triggerStarts it
- 3Set Error Notification ConfigSetLogic
- 4Retrieve Open IncidentsNotionService
- 5Clean Error DetailsCodeLogic
- 6Craft Digest MessageCodeLogic
- 7Classify Error SeverityCodeLogic
- 8Check Digest TransmissionIfLogic
- 9Build Incident InfoCodeLogic
- 10Deliver Daily Digest to SlackSlackService
- 11Search Existing IncidentsNotionService
- 12Check Incident ExistsIfLogic
- 13Prepare Incident UpdateCodeLogic
- 14Create New IncidentNotionService
- 15Update Incident in NotionNotionService
- 16Check for New AlertIfLogic
- 17Evaluate Repeated Alert NecessityIfLogic
- 18Post New Alert to SlackSlackService
- 19Skip New Alert NotificationNo OpLogic
- 20Post Repeated Alert to SlackSlackService
- 21Skip Repeated Alert NotificationNo OpLogic
How it's built
- Starts on
- A clock
- Steps
- 21, with 4 branches
- Size
- Large: read it before trusting it with anything live
- Connects to
- Notion, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Notion 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 21 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 21 steps before you point it at anything that matters.