PROJECT MANAGEMENT
Detect circular dependencies across the roadmap and backlog
When a new blocking link is added in Monday or Linear, traverses the combined dependency graph to detect cycles and alerts the team in Slack before a deadlock is committed.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook on new blocking linkHTTP webhook
- ActionLoad blocking edges from Monday and Linearmonday.com
- LogicRun cycle-detection traversal
- LogicExit if no cycle detected
- OutputAlert team in Slack with the loopSlack
What it does
Every time someone adds a blocking relationship in either tool, it walks the full cross-tool graph to check whether the new edge would create a cycle (A blocks B blocks C blocks A). If it would, the team is warned immediately so the impossible dependency can be removed.
When to use it
Use it when complex roadmaps accumulate dependencies that occasionally loop, stalling planning because no item can ever start. Catches the deadlock at write time instead of in a stuck sprint.
How it works
- 1A webhook fires when a new blocking link is created in Monday or Linear.
- 2An action loads the current blocking edges from both tools to assemble the full graph.
- 3A logic step runs a cycle-detection traversal starting from the newly added edge.
- 4A logic branch exits quietly if no cycle is found.
- 5The output posts a Slack alert naming the items in the loop and tagging the person who added the link.
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.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.
Log every dependency slip to a Notion register and email the affected leads
On any Asana dependency slip, appends a structured row to a Notion blocker register and emails the leads of the downstream teams so there is both an auditable record and a direct…
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.
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.
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.