Route multichannel support tickets with OpenAI, HubSpot, Jira, and Slack
Ready for 3.0What this workflow does
This AI workflow has 59 nodes and runs on Gmail events (plus 4 other triggers). Along the way it connects Gmail, OpenAI and Slack. It also calls api.hubapi.com over HTTP.
How it runs
Trigger: On Gmail events (plus 4 other triggers).
- Normalize Gmail Data (Code): runs custom JavaScript code
- Filter WAHA Messages (Code): runs custom JavaScript code
- Normalize Form Data (Code): runs custom JavaScript code
- Load SLA Config (Code): runs custom JavaScript code
- Format Error Payload (Code): runs custom JavaScript code
- Parse WAHA Data (Code): runs custom JavaScript code
- Search Breached Tickets (HTTP Request): calls an HTTP API
- Slack: uses Slack
- Load Configuration (Code): runs custom JavaScript code
- Check for Media (If): checks a condition and branches into true / false
…plus 43 more steps. See the full node list below.
Services it uses
HTTP calls to: api.hubapi.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.
- Still check Gmail Trigger below v1.4 runs as v1.4 (drafts skipped, max emails per poll) (When Gmail Received).
Nodes used (13)
- Gmail Trigger
n8n-nodes-base.gmailTrigger - Code
n8n-nodes-base.code - Webhook
n8n-nodes-base.webhook - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - n8n Form Trigger
n8n-nodes-base.formTrigger - n8n Form
n8n-nodes-base.form - Merge
n8n-nodes-base.merge - OpenAI
@n8n/n8n-nodes-langchain.openAi - Slack
n8n-nodes-base.slack - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Error Trigger
n8n-nodes-base.errorTrigger - No Operation, do nothing
n8n-nodes-base.noOp
From the author
Quick overview Analyze incoming support requests, classify intent and priority with AI, create Jira tickets, assign the correct team, send Slack notifications, and track SLA deadlines. Supports Gmail, WhatsApp, forms, HubSpot CRM, OpenAI, Jira, and Slack…