PROJECT MANAGEMENT
Push Monday roadmap date slips back to the Linear epic
When a planner moves a Monday roadmap item's timeline, it updates the linked Linear epic's target date and flags the engineering owner so the plan stays authoritative in both…
How it runs
The automated pipeline, trigger to output.
- TriggerMonday timeline column changedmonday.com
- LogicRequire linked epic ID + >1 day shift
- ActionRead current Linear epic stateLinear
- ActionUpdate Linear epic target dateLinear
- LogicBranch on slip later vs pulled earlier
- OutputAlert owner in Slack with date diffSlack
What it does
Closes the reverse direction of roadmap sync. When leadership reschedules a deliverable on the Monday board, this writes the new target date onto the corresponding Linear epic and notifies the epic's owner, so engineering isn't working against an outdated plan.
When to use it
Use it when planning conversations happen in Monday but execution tracking lives in Linear. It stops the common failure where exec moves a date and engineering never hears about it.
How it works
- 1A Monday webhook fires when a roadmap item's timeline column changes.
- 2A filter confirms the item has a stored Linear epic ID and the date actually moved by more than a day.
- 3The flow reads the current Linear epic to capture the old target date and owner.
- 4It updates the Linear epic's target date to match Monday.
- 5It branches: if the date slipped later, it posts a direct Slack DM-style alert to the owner; if it pulled earlier, it posts a lighter heads-up in the team channel.
- 6It logs the before/after dates in the Slack message for an audit trail.
Set it up
What you configure once, before turning it on.
- 1Connect monday.comVisual work management for teams.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Project Management workflows
Zoom Sprint-Retro Audio to Themed Linear Action Board
Transcribes a recorded Zoom sprint retrospective, clusters the discussion into themes, and creates assigned Linear issues for each action item with the spoken owner attached.
Escalate Overdue Cross-Team Dependencies to Owners and Stakeholders
Each morning checks Linear for dependency-labeled issues past their due date and nudges the owner in Slack, escalating to the requesting team's lead if it stays unresolved.
CEO-Authored Weekly Cross-Team Dependency Risk Briefing
Weekly, the CEO agent gathers all tracked dependencies across Linear and ClickUp, reasons about which handoffs threaten upcoming milestones.
Scan Notion Meeting Notes for Action Items and Open ClickUp Dependency Tasks
On a schedule, parses recently edited Notion meeting-notes pages for action items that one team owes another and creates a ClickUp task for each, with due date and owner mapped.
Sprint-Retro Recap to Slack with Owner DMs
After a Zoom retro, posts a themed recap to the team Slack channel and direct-messages each owner the specific action items they committed to during the call.
Turn GitHub Blocking Comments into Tracked Cross-Team Promises
When a reviewer comments that a PR is blocked waiting on another team, the flow registers a tracked dependency in Linear and notifies the team that owes the unblock.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
