Notify customers of resolved Jira bugs with Gmail, HubSpot, Slack and Sheets
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 18 nodes and runs on Jira events (jira:issue updated). Along the way it connects Jira Software, Gmail, HubSpot and Slack and 1 more. It also calls api.hubapi.com over HTTP.
How it runs
Trigger: On Jira events (jira:issue updated).
- Filter: Bug Resolved? (If): checks a condition and branches into true / false
- Normalize & Enrich Payload (Code): runs custom JavaScript code
- Deduplication Check (Code): runs custom JavaScript code
- Already Processed? (If): checks a condition and branches into true / false
- Has Customer Email? (If): checks a condition and branches into true / false
- Get Jira Issue Details (Jira Software): get
- Search HubSpot Contact (HTTP Request): calls api.hubapi.com (POST)
- Log: No Email Found (Code): runs custom JavaScript code
- Merge: merges the data from its input branches
- Alert: Manual Follow-Up (Slack): uses Slack
…plus 7 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)
- Jira Trigger
n8n-nodes-base.jiraTrigger - If
n8n-nodes-base.if - Code
n8n-nodes-base.code - Jira Software
n8n-nodes-base.jira - Merge
n8n-nodes-base.merge - Gmail
n8n-nodes-base.gmail - HubSpot
n8n-nodes-base.hubspot - Slack
n8n-nodes-base.slack - Google Sheets
n8n-nodes-base.googleSheets - HTTP Request
n8n-nodes-base.httpRequest
From the author
How it works This workflow automatically handles every resolved Jira bug by verifying the fix, notifying the customer, updating HubSpot, commenting on the Jira issue, alerting the team on Slack, and logging everything to Google Sheets — all without any manual…