The flow
Starts it 5Logic 6Service 2
The steps in the order they run, from what starts it.
- 1Receive maintenance requestWebhookStarts it
- 2Workflow configurationSetLogic
- 3Validate request and prevent duplicatesCodeLogic
- 4Is request valid?IfLogic
- 5Has this request already been processed?IfLogic
- 6Return validation errorRespond To WebhookStarts it
- 7Return duplicate acknowledgementRespond To WebhookStarts it
- 8Classify and route maintenance requestCodeLogic
- 9Is this an emergency?IfLogic
- 10Alert emergency review queueSlackService
- 11Alert routine review queueSlackService
- 12Return emergency acknowledgementRespond To WebhookStarts it
- 13Return review acknowledgementRespond To WebhookStarts it
How it's built
- Starts on
- Another system calling it
- Steps
- 13, with 3 branches
- 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 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.