Automate cross-project dependency tracking between Jira and Monday
Needs changesWhat this workflow does
This workflow has 10 nodes and runs on a schedule (legacy Cron node). Along the way it connects Monday.com, Gmail, Jira Software and Slack.
How it runs
Trigger: On a schedule (legacy Cron node).
- Fetch Open Jira Issues (Jira Software): get many
- Filter Dependencies (If): checks a condition and branches into true / false
- Extract Dependency Details (Function): runs custom JavaScript (legacy Function node)
- Compute Impact Score (Function): runs custom JavaScript (legacy Function node)
- Create Monday.com Item (Monday.com): work with board item
- Create Coordination Task (Jira Software): uses Jira Software
- Email Formatter (Code): runs custom JavaScript code
- Post to Slack (Slack): uses Slack
- Send Email Report (Gmail): uses Gmail
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 (Nightly Run): replace with Schedule Trigger.
- Function (legacy) in Extract Dependency Details, Compute Impact 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 (Nightly Run) | Schedule Trigger |
| Function (legacy) Extract Dependency Details, Compute Impact Score | Code node, mode 'Run Once for All Items' |
Nodes used (8)
- Cron
n8n-nodes-base.cron - If
n8n-nodes-base.if - Function
n8n-nodes-base.function - Monday.com
n8n-nodes-base.mondayCom - Gmail
n8n-nodes-base.gmail - Jira Software
n8n-nodes-base.jira - Slack
n8n-nodes-base.slack - Code
n8n-nodes-base.code
From the author
Description Keep your product and project teams perfectly aligned by automatically syncing task dependencies between Jira and Monday.com. This workflow ensures real-time visibility into cross-platform blockers and dependencies, allowing smoother delivery…