Triage and escalate HubSpot tickets to Jira with Slack SLA alerts
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 14 nodes and runs on a schedule (every 10 minutes). Along the way it connects HubSpot, Jira Software and Slack. It also calls api.hubapi.com over HTTP.
How it runs
Trigger: On a schedule (every 10 minutes).
- HubSpot: Search New Tickets (HTTP Request): calls api.hubapi.com (POST)
- Check: Are there tickets? (If): checks a condition and branches into true / false
- Loop: Process Tickets (Split Out): splits a list into separate items
- HubSpot: get (ticket)
- Filter: keeps only the items that match a condition
- HubSpot: Get Contact Data (HTTP Request): calls api.hubapi.com (POST)
- Code: runs custom JavaScript code
- Jira: Create Triage Ticket (Jira Software): uses Jira Software
- Slack: uses Slack
- Wait: waits 15 minutes
…plus 3 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.
Nodes used (10)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Split Out
n8n-nodes-base.splitOut - HubSpot
n8n-nodes-base.hubspot - Filter
n8n-nodes-base.filter - Code
n8n-nodes-base.code - Jira Software
n8n-nodes-base.jira - Slack
n8n-nodes-base.slack - Wait
n8n-nodes-base.wait
From the author
This workflow automates the prioritization and escalation of customer support tickets. It acts as an intelligent triage system that identifies high-value customers and potential churn risks in HubSpot, syncs them to Jira, and enforces response times via Slack…