Escalate overdue and blocked Jira tickets with Gmail and Google Chat
Ready for 3.0What this workflow does
This workflow has 33 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Gmail and Jira Software.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- ⚙️ CONFIG (Edit Fields (Set)): sets 4 fields: JIRA_DOMAIN, JIRA_PROJECT_KEY, MANAGER_EMAILS…
- GET_JIRA_ISSUES (Jira Software): get many
- GET_ISSUES_LIST (Code): runs custom JavaScript code
- Loop Over Items (Loop Over Items (Split in Batches)): loops over the items in batches
- ISSUE_DATE_INSIGHTS (Code): runs custom JavaScript code
- ROUTES (Switch): routes items into 5 branches
- SEND_DUEDATE_REMINDER (Gmail): uses Gmail
- IS_OVERDUE_BETWEEN (If): checks a condition and branches into true / false
- MANAGER_ESCALATION (Gmail): uses Gmail
- GET_ISSUE_CHANGELOG (Jira Software): changelog
…plus 20 more steps. See the full node list below.
Services it uses
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 (14)
- Manual Trigger
n8n-nodes-base.manualTrigger - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - No Operation, do nothing
n8n-nodes-base.noOp - Switch
n8n-nodes-base.switch - Gmail
n8n-nodes-base.gmail - Schedule Trigger
n8n-nodes-base.scheduleTrigger - If
n8n-nodes-base.if - Aggregate
n8n-nodes-base.aggregate - Code
n8n-nodes-base.code - Merge
n8n-nodes-base.merge - Jira Software
n8n-nodes-base.jira - Wait
n8n-nodes-base.wait - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set
From the author
How it works - Fetches all open sprint tickets daily from your Jira project - Analyzes each ticket for overdue days and blocked status - Routes to the right escalation level: assignee email → team Google Chat alert → manager escalation Set up steps - Add your…