The flow
Starts it 2Logic 6Service 11
The steps in the order they run, from what starts it.
- 1Ticket WebhookWebhookStarts it
- 2Error TriggerError triggerStarts it
- 3Normalize TicketSetLogic
- 4Notify Team of FailureSlackService
- 5Fetch Customer HistoryHttp RequestService
- 6Build ContextCodeLogic
- 7AI Classify TicketHttp RequestService
- 8Parse ClassificationCodeLogic
- 9Route by UrgencySwitchLogic
- 10Notify On-Call (Critical)SlackService
- 11Notify Senior Agent (High)SlackService
- 12Vector KB SearchHttp RequestService
- 13AI Generate Draft ResponseHttp RequestService
- 14Parse DraftCodeLogic
- 15Confidence >= 0.8?IfLogic
- 16Send Auto-ResolutionHttp RequestService
- 17Escalate to HumanSlackService
- 18Update Ticket StatusHttp RequestService
- 19Log to Analytics DBHttp RequestService
How it's built
- Starts on
- Another system calling it
- Steps
- 19, with 2 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. 19 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 19 steps before you point it at anything that matters.