The flow
Starts it 1Logic 4Service 4
The steps in the order they run, from what starts it.
- 1Receive Uptime AlertWebhookStarts it
- 2Filter for Critical StatusIfLogic
- 3Create New Jira IncidentJiraService
- 4Get On-Call Channel MembersSlackService
- 5Split/Process Each MemberSplit In BatchesLogic
- 6Select Active On-Call UserCodeLogic
- 7Check Slack User PresenceSlackService
- 8Notify Selected UserSlackService
- 9Collect & Set Final DataSetLogic
How it's built
- Starts on
- Another system calling it
- Steps
- 9, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Jira, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Jira and Slack accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on another system calling it.
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. 9 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.
Before you run itNothing 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 9 steps before you point it at anything that matters.