PROJECT MANAGEMENT
Mirror Monday roadmap blockers as Linear blocking issues
When a Monday roadmap item is marked as blocked, this creates or updates a corresponding blocking relationship on the linked Linear issue so engineering sees the dependency…
How it runs
The automated pipeline, trigger to output.
- TriggerMonday item status changes to Blockedmonday.com
- LogicResolve linked Linear issue IDs for item and blocker
- ActionCreate blocked-by relation in LinearLinear
- ActionAdd blocked label and dependency commentLinear
- OutputConfirm sync in Monday item update feedmonday.com
What it does
Keeps a roadmap board and the engineering backlog in lock-step. When a planner flags a roadmap item on Monday as blocked by another item, the matching Linear issue gets a `blocks`/`blocked-by` link, a comment explaining the dependency, and a `blocked` label.
When to use it
Use it when product manages sequencing on Monday but engineers live in Linear, and blocking relationships keep getting lost in translation. It removes the manual step of re-typing dependencies into a second tool.
How it works
- 1A Monday status column change to "Blocked" fires the trigger with the item and its dependency column.
- 2A logic step reads the linked Linear issue IDs stored on both the blocked item and its blocker; if either link is missing, the run exits cleanly.
- 3An action calls Linear to create the `blocked-by` relation between the two issues.
- 4A second Linear action adds the `blocked` label and posts a comment naming the Monday item and reason.
- 5The output posts a one-line confirmation back to the Monday item's update feed so the planner sees the sync landed.
Set it up
What you configure once, before turning it on.
- 1Connect monday.comVisual work management for teams.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.