The flow
Starts it 1Logic 6Service 5
The steps in the order they run, from what starts it.
- 1Daily OKR Sync TriggerSchedule triggerStarts it
- 2Fetch OKRs from Monday.comMonday ComService
- 3Map Monday Fields → Standard KR SchemaSetLogic
- 4Split KR → Epics MapperCodeLogic
- 5Join KR + Epic Data (SQL Merge)MergeLogic
- 6Fetch Jira Epic DetailsJiraService
- 7Compute KR Progress & VarianceCodeLogic
- 8Normalize Jira ResponseCodeLogic
- 9Update KR Status on MondayMonday ComService
- 10Aggregate Final Results for ReportingAggregateLogic
- 11Post Slack Variance ReportSlackService
- 12Email Variance Digest (Outlook)Microsoft OutlookService
How it's built
- Starts on
- A clock
- Steps
- 12
- Size
- Medium: a working afternoon
- Connects to
- Jira, Outlook, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Jira, Outlook and Slack accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 12 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 12 steps before you point it at anything that matters.