PROJECT MANAGEMENT
Auto-Assign Unblock Owners to Stalled Asana Dependencies
When an Asana task has been waiting on a blocking dependency past its threshold, this workflow assigns the blocker's project lead as the explicit unblock owner and DMs them…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionQuery Asana for tasks blocked by incomplete dependenciesAsana
- LogicFilter to blockers stalled past age threshold
- ActionResolve blocking task's project lead and assign as unblock ownerAsana
- OutputDM the assigned owner with what to clear in SlackSlack
What it does
Blocked tasks often sit because no one is named as the person responsible for clearing the upstream blocker. This workflow watches for tasks blocked longer than a set threshold, identifies the upstream blocking task, and assigns its project lead as the accountable unblock owner, then notifies them directly.
When to use it
Use it when dependency chains cross team boundaries and blocked work quietly ages because accountability for the blocker is ambiguous. Great for operations leads who want every stalled dependency to have one named owner.
How it works
- 1A daily schedule triggers the scan.
- 2The workflow queries Asana for tasks marked blocked by an incomplete dependency.
- 3A logic step filters to blockers stalled past the configured age threshold.
- 4For each, it resolves the blocking task's project lead from Asana project membership.
- 5It assigns that lead to the blocking task and adds an "unblock-owner" tag.
- 6It sends the owner a Slack DM with the blocked downstream count and a link to the blocker.
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.