The flow
Starts it 1Logic 8Service 5
The steps in the order they run, from what starts it.
- 1Every 15 Minutes ScheduleSchedule triggerStarts it
- 2Retrieve Current IncidentsService NowService
- 3Set Incident Field DataSetLogic
- 4Group Incidents by CategoryCodeLogic
- 5Batch Process IncidentsSplit In BatchesLogic
- 6Compute Breach ProbabilityCodeLogic
- 7Retrieve Past ResolutionsService NowService
- 8Limit to 10 ItemsLimitLogic
- 9Pause for 1 SecondWaitLogic
- 10Check Breach Risk > 70%IfLogic
- 11Escalate SLA Breach IncidentService NowService
- 12Continue Without ActionNo OpLogic
- 13Add Note to IncidentService NowService
- 14Post Alert to Slack ChannelSlackService
How it's built
- Starts on
- A clock
- Steps
- 14, with 1 branch, 2 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- Slack
- 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?
Plan an afternoon. 14 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 14 steps before you point it at anything that matters.