PROJECT MANAGEMENT
Detect Circular Dependency Deadlocks Across Asana Projects
Scans dependency links across all Asana projects on a schedule, finds circular chains where tasks block each other.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionFetch tasks and dependency links from all Asana projectsAsana
- LogicBuild dependency graph and detect circular deadlocks
- LogicChoose break-point task with most downstream blocked work
- OutputPost each deadlock cycle with recommended unblock to SlackSlack
What it does
Every morning this workflow walks the dependency graph across all of your Asana projects, finds true circular deadlocks (Task A blocks B, B blocks C, C blocks A), and surfaces them in Slack before they silently stall a release. It also names the cheapest task to unblock first so the cycle can be broken with one action.
When to use it
Run it when work spans many Asana projects and dependencies are added by different teams, so no single person can see a loop forming. Ideal for program managers coordinating cross-team launches where a hidden cycle freezes everyone.
How it works
- 1A daily schedule fires the run.
- 2The workflow pulls every task and its `dependencies`/`dependents` from each Asana project.
- 3A logic step builds the directed graph and runs cycle detection, keeping only chains that form a closed loop.
- 4For each cycle it picks the break-point task (the one with the most downstream blocked work).
- 5It posts a Slack message per deadlock listing the full chain, owners, and the recommended task to unblock first.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.