The flow
Starts it 2Logic 8Service 7
The steps in the order they run, from what starts it.
- 1Webhook - New Crash ReportWebhookStarts it
- 2Manual Trigger - Test RunManual triggerStarts it
- 3Set - ConfigSetLogic
- 4Set - Sample Crash PayloadSetLogic
- 5JS - Parse Stack Trace & Extract FramesCodeLogic
- 6SplitOut - One Item Per Candidate FrameSplit OutLogic
- 7HTTP Request - Fetch File Commit HistoryHttp RequestService
- 8HTTP Request - Fetch File BlameHttp RequestService
- 9Merge - Combine Commit History & BlameMergeLogic
- 10JS - Aggregate Candidate Frame EvidenceCodeLogic
- 11HTTP Request - Claude: Correlate Crash With Code ChangesHttp RequestService
- 12JS - Parse Correlation ResultCodeLogic
- 13IF - Confidence Meets Auto-Assign ThresholdIfLogic
- 14HTTP Request - Create Task (High Confidence)Http RequestService
- 15HTTP Request - Create Task (Needs Triage)Http RequestService
- 16Slack - Notify Likely Responsible AuthorSlackService
- 17Slack - Notify Triage ChannelSlackService
How it's built
- Starts on
- Another system calling it
- Steps
- 17, with 1 branch
- 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. 17 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 17 steps before you point it at anything that matters.