Automate Service Ticket Triage with GPT-4o & Taiga
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: AI Agent v1 (old agent modes). 1 breaking item(s) found. Static check, last run 2026-10-19.
What to replace before upgrading
| Removed in 3.0 | Replace with |
|---|---|
| AI Agent v1 (old agent modes) AI Agent (v1.9) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Rarely used nodes in this template: n8n-nodes-base.taigaTrigger, n8n-nodes-base.taiga
Nodes used (7)
- Taiga Trigger
n8n-nodes-base.taigaTrigger - If
n8n-nodes-base.if - Taiga
n8n-nodes-base.taiga - Switch
n8n-nodes-base.switch - AI Agent
@n8n/n8n-nodes-langchain.agent - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi
What it does
Usecase: When a new service ticket is created in Taiga, it's often unclear whether it contains sufficient details to begin work. This workflow automates the triage process by: 1. Using an AI model to extract key information from the ticket description. 2. Automatically assigning values for: - Type (Bug, Enhancement, Onboarding, Question) - Severity (Wishlist, Minor, Normal, Important, Critical) - Priority (Low, Normal, High) - Status (New, Needs More Info, etc.) 3. Detecting missing critical data and blocking the ticket if incomplete. Setup instructions here: https://github.com/emooney/ServiceTicketTriageHelper