Classify and route support tickets via webhooks using RapidAPI
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 8 nodes and runs when an HTTP POST request hits its webhook URL. It uses only n8n's built-in nodes. It also calls support-ticket-triage.p.rapidapi.com over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Normalize Ticket Content (Edit Fields (Set)): sets 1 field: ticket
- Post to RapidAPI for Analysis (HTTP Request): calls support-ticket-triage.p.rapidapi.com (POST)
- Check Ticket Priority (If): checks a condition and branches into true / false
- Prepare Escalation Alert (Edit Fields (Set)): sets 1 field: alert_message
- Prepare Standard Ticket Update (Edit Fields (Set)): sets 1 field: helpdesk_update
HTTP calls to: support-ticket-triage.p.rapidapi.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (5)
- Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - No Operation, do nothing
n8n-nodes-base.noOp
From the author
Quick overview This workflow receives new support tickets via a webhook, sends the ticket text to the Support Ticket Triage & Classifier API on RapidAPI to extract structured triage fields, and routes high-priority tickets to an escalation path while sending…