PROJECT MANAGEMENT
Alert downstream owners when an Asana blocker misses its due date
Watches Asana tasks marked as blockers and, when one passes its due date incomplete, finds every task that depends on it and DMs each downstream owner in Slack with the slipped…
How it runs
The automated pipeline, trigger to output.
- TriggerAsana task passes due date still incompleteAsana
- LogicKeep only tasks tagged 'blocker'
- ActionFetch dependents and resolve their assigneesAsana
- LogicBranch: at least one dependent still open
- OutputDM each downstream owner in SlackSlack
What it does
When a task tagged as a blocker in Asana crosses its due date without being completed, this workflow traces its dependency graph, identifies every downstream task now at risk, and sends each downstream owner a direct Slack message naming the slipped blocker and their specific impacted task.
When to use it
Run this on projects where one team's deliverable gates several others and a silent slip cascades into missed launches. It turns a quiet overdue blocker into targeted, owner-by-owner warnings before the dependent work stalls.
How it works
- 1Asana trigger fires when a task's due date passes while it is still incomplete.
- 2A filter keeps only tasks carrying the "blocker" tag, discarding ordinary overdue items.
- 3An Asana call pulls the task's dependents and resolves each downstream task's assignee.
- 4A branch checks that at least one dependent exists and is not yet done.
- 5For each at-risk downstream task, a Slack direct message names the slipped blocker, the new exposure, and a link.
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
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.
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.
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.
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…
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.