The flow
Starts it 1Logic 7Service 5
The steps in the order they run, from what starts it.
- 1Receive IoT Machine AlertWebhookStarts it
- 2Check Failure ThresholdIfLogic
- 3Create Jira Maintenance TicketJiraService
- 4Fetch Technician Channel MembersSlackService
- 5Prepare Technician Iteration DataSetLogic
- 6Loop Through TechniciansSplit In BatchesLogic
- 7Select Final Available TechnicianCodeLogic
- 8Get Technician Presence StatusSlackService
- 9Check If Any Technician AvailableIfLogic
- 10Check If Technician ActiveIfLogic
- 11Send Technicians Alert (Active Tech)SlackService
- 12Escalate to Ops Emergency ChannelSlackService
- 13Format Technician Availability ResultSetLogic
How it's built
- Starts on
- Another system calling it
- Steps
- 13, with 3 branches, 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. 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.