The flow
Starts it 4Logic 13Service 5
The steps in the order they run, from what starts it.
- 1New TicketWebhookStarts it
- 2Error TriggerError triggerStarts it
- 3Normalize DataCodeLogic
- 4Format ErrorCodeLogic
- 5Valid Ticket?IfLogic
- 6Error AlertSlackService
- 7Categorize TicketCodeLogic
- 8Validation ErrorCodeLogic
- 9Check DuplicateHttp RequestService
- 10Respond 400Respond To WebhookStarts it
- 11Not Duplicate?IfLogic
- 12Assign SLACodeLogic
- 13Format SuccessCodeLogic
- 14Create TicketHttp RequestService
- 15Respond 200Respond To WebhookStarts it
- 16Route by PrioritySwitchLogic
- 17Format CriticalCodeLogic
- 18Format HighCodeLogic
- 19Format MediumCodeLogic
- 20Format LowCodeLogic
- 21Notify TeamSlackService
- 22Send ConfirmationGmailService
How it's built
- Starts on
- Another system calling it
- Steps
- 22, with 3 branches
- Size
- Large: read it before trusting it with anything live
- Connects to
- Gmail, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail 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?
Take your time. At 22 steps it is large: read it before trusting it with anything live.
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 22 steps before you point it at anything that matters.