Triage support tickets and draft AI replies with CometAPI, Slack and Gmail
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 9 nodes and runs when someone submits an n8n form (“Submit a Support Ticket”) (plus 1 other trigger). Along the way it connects Slack, Gmail and Cometapi (community).
How it runs
Trigger: When someone submits an n8n form (“Submit a Support Ticket”) (plus 1 other trigger).
- Set Ticket Fields (Edit Fields (Set)): sets 4 fields: Name, Email, Subject…
- AI Ticket Issue Analysis (Comet Api): uses Comet Api
- Parse AI Analysis (Code): runs custom JavaScript code
- Generate Reply Suggestion (Comet Api): uses Comet Api
- Route by Ticket Issue (Switch): routes items into 3 branches
- Post to Slack Channel (Slack): uses Slack
- Send Email via Gmail (Gmail): work with draft
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @cometapi-dev/n8n-nodes-cometapi is verified or supports 3.0 (used in AI Ticket Issue Analysis, Generate Reply Suggestion).
Nodes used (8)
- n8n Form Trigger
n8n-nodes-base.formTrigger - Slack
n8n-nodes-base.slack - Gmail Trigger
n8n-nodes-base.gmailTrigger - Gmail
n8n-nodes-base.gmail - Edit Fields (Set)
n8n-nodes-base.set - Comet Api
@cometapi-dev/n8n-nodes-cometapi.cometApi - Code
n8n-nodes-base.code - Switch
n8n-nodes-base.switch
From the author
Quick overview This workflow ingests support tickets from an n8n Form or from Gmail, uses CometAPI to classify each ticket (category, urgency, sentiment) and generate a suggested reply, then routes high/medium urgency tickets to Slack and creates a Gmail…