PROJECT MANAGEMENT
Escalate to Slack when an upstream Asana dependency slips its due date
Watches Asana for tasks that just had their due date pushed, and if any downstream task depends on them.
How it runs
The automated pipeline, trigger to output.
- TriggerAsana task due date pushed laterAsana
- ActionFetch task dependentsAsana
- LogicSkip if no downstream dependents
- ActionResolve dependent task owner and committed dateAsana
- OutputPost blocker alert to downstream Slack channelSlack
What it does
When an Asana task moves its due date later, this workflow checks whether any other task lists it as a dependency. If it does, it raises a clear cross-team blocker alert in Slack so the downstream owner finds out the moment the commitment changes, not at standup three days later.
When to use it
Use it when your delivery plan has hard hand-offs between teams (design to eng, eng to QA, vendor to launch) and a silent slip on one task quietly torpedoes a date on another. It turns an invisible schedule drift into an immediate, addressed-to-the-right-person notification.
How it works
- 1Asana fires on a task whose `due_on` field changed to a later date.
- 2The workflow pulls the task's dependents from Asana to see who is downstream.
- 3A filter drops the run if there are no dependents (nothing is blocked).
- 4For each dependent it fetches the assignee and the originally committed date.
- 5A blocker message is posted to the dependent team's Slack channel with old date, new date, slip length, and the blocked owner @-mentioned.
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.