The flow
Starts it 4Logic 6Service 6
The steps in the order they run, from what starts it.
- 1Webhook - Receive TicketWebhookStarts it
- 2Email Trigger - Support InboxEmail Read ImapService
- 3Error HandlerError triggerStarts it
- 4Normalize InputCodeLogic
- 5Error ResponseRespond To WebhookStarts it
- 6AI - Classify & PrioritizeHttp RequestService
- 7Parse AI ResponseCodeLogic
- 8Switch - Priority RouteSwitchLogic
- 9Slack - Critical AlertSlackService
- 10Slack - High PrioritySlackService
- 11Check Auto-Reply EligibilityCodeLogic
- 12IF - Can Auto-ReplyIfLogic
- 13Send Auto-Reply EmailEmail SendService
- 14Google Sheets - Log TicketGoogle SheetsService
- 15Build ResponseCodeLogic
- 16Respond to WebhookRespond To WebhookStarts it
How it's built
- Starts on
- Another system calling it
- Steps
- 16, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- Email, Google Sheets, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Email, Google Sheets 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. 16 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 16 steps before you point it at anything that matters.