Track Jira epic health with automated risk alerts via Slack, Monday & Sheets
Needs changesNeeds changes. This template uses 2 thing(s) that n8n 3.0 removes: Cron, Function (legacy). 2 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 10 nodes and runs on a schedule (legacy Cron node). Along the way it connects Jira Software, Slack, Monday.com and Google Sheets.
How it runs
Trigger: On a schedule (legacy Cron node).
- Fetch All Epics from Jira (Jira Software): get many
- Split Epics for Processing (Function): runs custom JavaScript (legacy Function node)
- Fetch Epic + Linked Issues (Jira Software): get
- Calculate Health Score (Function): runs custom JavaScript (legacy Function node)
- Is Score > 0.6 (At Risk)? (If): checks a condition and branches into true / false
- Update Epic in Jira (Jira Software): update
- Alert Slack Channel (Slack): uses Slack
- Update Monday.com Pulse (Monday.com): update
- Log to Google Sheets (Google Sheets): append
Services it uses
Before you upgrade to n8n 3.0
2 things in this workflow are removed in n8n 3.0. Fix them before you upgrade:
- Cron in Trigger Every 6 Hours: replace with Schedule Trigger.
- Function (legacy) in Split Epics for Processing, Calculate Health Score: replace with Code node, mode 'Run Once for All Items'.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Cron Trigger Every 6 Hours | Schedule Trigger |
| Function (legacy) Split Epics for Processing, Calculate Health Score | Code node, mode 'Run Once for All Items' |
Nodes used (7)
- Cron
n8n-nodes-base.cron - Jira Software
n8n-nodes-base.jira - Function
n8n-nodes-base.function - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack - Monday.com
n8n-nodes-base.mondayCom - Google Sheets
n8n-nodes-base.googleSheets
From the author
Description: Transform your Jira project management workflow with this intelligent n8n automation template that continuously tracks, scores, and reports the health of Jira Epics. The automation runs every 6 hours, fetches all active Epics, analyzes linked…