PROJECT MANAGEMENT
Flag downstream Asana tasks blocked by an at-risk milestone
When an Asana milestone slips or is marked at-risk, walks its dependency chain to find every downstream task that will be delayed, and posts a ranked blast-radius report to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerAsana milestone updated (date or status field)Asana
- LogicKeep only changes that breach the deadline or set At Risk
- ActionFetch downstream dependent tasks, recursing one levelAsana
- LogicRank blocked tasks by remaining slack
- OutputPost ranked blast-radius report to Slack channelSlack
What it does
Watches a portfolio of Asana milestones. The moment one is marked at-risk or its due date moves past the project deadline, this template traces the full dependency tree downstream and reports exactly which tasks, owners, and sub-deadlines are now in jeopardy.
When to use it
Run this on any project where a single late milestone quietly cascades into missed launch dates. Instead of a PM manually clicking through dependencies, you get an instant blast-radius readout the moment risk appears.
How it works
- 1An Asana milestone is updated (due date changed or a custom "Status" field set to At Risk).
- 2A filter confirms the change actually pushes the milestone past its committed date or flips it to a risk state.
- 3The flow fetches all tasks that list this milestone as a dependency, then recurses one level further to capture second-order blockers.
- 4It scores each downstream task by slack remaining (due date minus new projected start) to rank what breaks first.
- 5A Slack message lands in the project channel with the ranked blocked-task list, owners @-mentioned, and a deep link back to the milestone.
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.