Monitor and report OKR variance from Monday.com and Jira via Slack and Email
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 12 nodes and runs on a schedule (every day). Along the way it connects Monday.com, Jira Software, Slack and Microsoft Outlook.
How it runs
Trigger: On a schedule (every day).
- Fetch OKRs from Monday.com (Monday.com): get many (board item)
- Map Monday Fields → Standard KR Schema (Edit Fields (Set)): sets 11 fields: id, name, created_at…
- Split KR → Epics Mapper (Code): runs custom JavaScript code
- Join KR + Epic Data (SQL Merge) (Merge): merges the data from its input branches
- Fetch Jira Epic Details (Jira Software): get
- Compute KR Progress & Variance (Code): runs custom JavaScript code
- Normalize Jira Response (Code): runs custom JavaScript code
- Update KR Status on Monday (Monday.com): change multiple column values (board item)
- Aggregate: combines items into one
- Post Slack Variance Report (Slack): uses Slack
…plus 1 more step. 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 (9)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Monday.com
n8n-nodes-base.mondayCom - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - Jira Software
n8n-nodes-base.jira - Merge
n8n-nodes-base.merge - Aggregate
n8n-nodes-base.aggregate - Slack
n8n-nodes-base.slack - Microsoft Outlook
n8n-nodes-base.microsoftOutlook
From the author
Description Synchronize OKRs (Objectives and Key Results) between Monday.com and Jira to automatically calculate progress variance, update dashboards, and share variance reports via Slack and Outlook. This workflow ensures teams have accurate, real-time…