Claude Code n8n Support Routing: Auto-Classify Tickets

Claude Code n8n support ticket routing uses Claude Code connected to n8n via the n8n-mcp MCP server to build an AI-powered ticket classification and routing system in 12 minutes. When a ticket arrives via Intercom or Zendesk webhook, Claude or OpenAI classifies the urgency level (P1-P4) and issue type (billing, technical, feature request, account). The classification drives routing: P1 critical issues trigger Slack alerts to the on-call team with escalation, P2-P3 route to team channels, P4 feature requests log for product. Build time drops from 60 minutes manual to 12 minutes.

[ STAT ] 69% of customers expect immediate responses. Average first response time is 12 hours. — Zendesk Customer Experience Trends Report, 2025

THE REAL PROBLEM

Support teams waste 20-30% of handle time on ticket triage — reading the ticket, determining urgency, identifying the right team, and routing manually. For a team handling 500 tickets per week at 5 minutes each for triage, that is 42 hours of overhead per week. According to Zendesk's 2025 Customer Experience Trends Report, 69% of customers expect immediate responses, yet the average first response time across industries is 12 hours. The bottleneck is not resolution — it is classification and routing. Each ticket must be read, categorized, and directed before any team can act on it. Manual triage is also inconsistent: P1 critical issues get buried in the queue because the urgency signal is missed. Claude Code and n8n connected via MCP solve this with AI-powered classification that evaluates every ticket in 3-5 seconds with 90%+ accuracy.

WHAT IT DOES

This workflow uses Claude Code connected to n8n via the n8n-mcp MCP server to build an intelligent support ticket routing system. When a ticket arrives via Intercom or Zendesk webhook, the workflow sends the ticket content through Claude or OpenAI for classification — determining urgency level (P1-P4), issue type (billing, technical, feature request, account), and the required team. The classification output drives routing logic. P1 critical issues get immediate Slack alerts to the on-call team with a phone escalation path. P2-P3 issues route to the appropriate team channel. P4 feature requests are logged for the product team. Every ticket is logged in Google Sheets with classification metadata.

[TOOL: Claude Code v2.1.154+] AI workflow builder. MCP mode constructs the classification pipeline.

[TOOL: n8n v1.80+] Workflow execution engine. Webhook, OpenAI, Switch, Slack, Google Sheets nodes.

[TOOL: OpenAI / Claude API] Ticket text classification into P1-P4 urgency and issue type.

[TOOL: Intercom / Zendesk] Source of tickets. Destination for AI-generated tags.

[TOOL: Slack] Alert delivery per routing path.

[TOOL: Google Sheets] Ticket log and analysis database.

WHO THIS IS BUILT FOR

FOR support team leads at SaaS companies handling 200-1000+ tickets per week SITUATION: Your team spends 3-5 minutes per ticket on manual triage. PAYOFF: AI classifies urgency and type in 3 seconds. Tickets arrive in the right team channel pre-tagged.

FOR customer success managers with SLA-based support tiers SITUATION: P1 critical issues get lost because manual triage misses urgency signals. PAYOFF: P1 tickets trigger Slack alerts with escalation path. SLA compliance guaranteed by automated routing.

FOR operations managers tracking support metrics SITUATION: No visibility into ticket volume by type or team response times. PAYOFF: Every ticket logged in Google Sheets with classification. Weekly reports on routing accuracy and SLA.

HOW IT RUNS STEP BY STEP

Webhook Trigger Setup (Claude Code MCP — 1 min) Input: Intercom or Zendesk webhook URL Action: Claude adds n8n Webhook node configured to receive incoming ticket payloads Output: Tickets flow into n8n from the support platform
Data Extraction (Claude Code MCP — 30 sec) Input: Raw ticket payload with nested JSON Action: Claude adds a Code node that extracts key fields: ticket ID, subject, description, customer email Output: Clean ticket object with normalized field names
AI Classification (Claude Code MCP — 1 min) Input: Ticket subject and description text Action: Claude adds an OpenAI node with a classification prompt that returns urgency, issue type, and team Output: Classification object with urgency level, issue category, and team assignment
Routing Decision (Claude Code MCP — 30 sec) Input: Classification object Action: Claude adds a Switch node with rules for each routing path Output: Routed ticket with destination channel and notification format
Slack Notification (Claude Code MCP — 30 sec) Input: Routed ticket with classification Action: Claude adds Slack node — P1 gets @here with red badge, standard gets blue info card Output: Slack message posted to appropriate channel
Google Sheets Logging (Claude Code MCP — 30 sec) Input: Ticket ID, classification, route, timestamp Action: Claude adds Google Sheets node that appends a row with all metadata Output: Persistent log for analysis
Ticket Tag Update (Claude Code MCP — 30 sec) Input: Original ticket ID + classification tags Action: Claude adds Intercom or Zendesk node that updates the ticket with AI-generated tags Output: Ticket updated in source system with classification visible to agents

SETUP AND TOOLS

Step 1: Restart n8n fully. Enable MCP, generate access token, copy immediately.

Step 2: Connect Claude Code via MCP add command with your N8N_API_URL and N8N_API_KEY.

Step 3: Prompt: 'Build an n8n support ticket routing workflow. When a webhook receives a ticket from Intercom, classify the urgency as P1-P4 and type as billing, technical, feature, or account using OpenAI. Route P1 to on-call Slack with @here, P2-P3 to team channel, P4 to product log. Log everything in Google Sheets and tag the ticket in Intercom.'

Step 4: The classification prompt needs examples of each urgency level. Include a few-shot: 'P1: system down for all users. P2: feature broken for one user. P3: cosmetic issue. P4: feature request.'

[TOOL: Claude Code] Include examples in your prompt for accurate classification.

THE NUMBERS

[ STAT ] 69% of customers expect immediate responses. — Zendesk CX Trends Report, 2025

KPI rows

Build time: 60 minutes manual to 12 minutes with Claude Code MCP
Triage time: 3-5 minutes manual to 3-5 seconds automated
First response SLA: 12 hours average to under 5 minutes for P1
Classification accuracy: 70-80% manual to 90%+ with good prompts
First-week win: 100 tickets classified and routed without intervention

WHAT IT CANNOT DO

Cannot classify accurately without prompt tuning (moderate): Initial accuracy may be below 90%. Plan 1-2 hours testing with 50 historical tickets to refine the classification prompt.
Cannot handle webhook schema changes automatically (moderate): Intercom and Zendesk update webhook schemas periodically. Monitor for extraction errors after platform updates.
Cannot prevent P1 alert fatigue (minor): If classification over-assigns P1 urgency, the on-call team will experience alert fatigue. Set a conservative threshold.
Cannot scale to 1000+ tickets per day without queue management (minor): n8n execution queue may lag at high volume. Monitor queue depth.

START IN 12 MINUTES

Restart n8n and enable MCP. Copy the access token.
Connect Claude Code via MCP add command.
Prompt Claude to build the classification and routing workflow.
Test with sample tickets from each urgency level.
Tune the classification prompt with 10-20 examples per category.
Deploy with the Intercom or Zendesk webhook.

FAQ

Q: What is Claude Code n8n support ticket routing? A: It is an AI-powered system that classifies incoming support tickets by urgency and type, routes them to the correct team via Slack, and logs everything in Google Sheets.

Q: How long does it take to set up? A: 12 minutes with Claude Code MCP plus 1-2 hours for classification prompt tuning with historical tickets.

Q: How accurate is the AI classification? A: With good prompt engineering and few-shot examples, accuracy reaches 90%+. Initial accuracy may be lower before tuning.

Q: Does it work with both Intercom and Zendesk? A: Yes. Claude Code can configure webhook nodes for either platform. The data extraction step normalizes the payload regardless of source.

Q: What happens when a P1 ticket is detected? A: The workflow sends a Slack alert to the on-call channel with an @here mention, red urgency badge, and escalation path instructions.

SOURCES

[ STAT ] 69% expect immediate responses, average first response 12 hours — Zendesk CX Trends Report, 2025 [ STAT ] Build time 4-12 hours to 15-45 minutes — Ability.ai, 2026

Sources: https://github.com/czlonkowski/n8n-mcp, https://medium.com/@alexp/claude-code-n8n-self-building-automation, https://ability.ai/reports/ai-workflow-automation-benchmarks, https://www.zendesk.com/reports/customer-experience-trends/, https://docs.n8n.io/advanced-ai/mcp/