The flow
Starts it 3Logic 6Service 6
The steps in the order they run, from what starts it.
- 1Webhook (Azure DevOps Service Hook)WebhookStarts it
- 2Cron (Daily Digest)CronStarts it
- 3Manual Trigger (Backfill/Test)Manual triggerStarts it
- 4Merge TriggersMergeLogic
- 5Normalize PayloadSetLogic
- 6Route by Event TypeSwitchLogic
- 7Slack → Digest PlaceholderSlackService
- 8HTTP Enrich Work Item (ADO)Http RequestService
- 9Score & PriorityCodeLogic
- 10Data Store Get (dedupKey)Data StoreService
- 11Already Processed?IfLogic
- 12Data Store Set (TTL 6h)Data StoreService
- 13Is P0 Alert?IfLogic
- 14Slack → #incidents (P0)SlackService
- 15Slack → #daily-triage (P1/P2)SlackService
How it's built
- Starts on
- Another system calling it
- Steps
- 15, 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. 15 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 15 steps before you point it at anything that matters.