PROJECT MANAGEMENT

Aging-blocker escalation ladder for Asana dependencies

Watches Asana tasks marked as blocked and escalates them in tiers — a nudge to the assignee at 2 days, a program-lead ping at 5 days, and a leadership rollup at 10 days.

CategoryProject Management
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerIntraday schedule fires
  • ActionList open blocked Asana tasksAsanaAsana
  • LogicCompute age and bucket into escalation tier
  • LogicBranch to the matching tier audience
  • OutputSend tier-specific Slack escalationSlack

What it does

This workflow monitors Asana tasks tagged as blocking a cross-team dependency and applies a time-based escalation ladder. The longer a blocker sits untouched, the higher it climbs: a gentle assignee reminder first, then a program-lead ping, then a leadership rollup. Each tier routes to a different Slack destination.

When to use it

Use it when a single daily digest isn't enough and you need graduated pressure — quiet nudges for fresh blockers, loud escalation for ones that have been ignored for over a week.

How it works

  1. 1A schedule runs the check a few times a day.
  2. 2The workflow lists Asana tasks with the dependency/blocked tag that are still open.
  3. 3For each, it computes age since the task was last modified.
  4. 4A branch routes the task by age tier: 2-day, 5-day, or 10-day-plus.
  5. 5Tier 1 DMs the assignee, Tier 2 posts to the program-lead channel, and Tier 3 compiles a leadership rollup.
  6. 6The matching Slack message is sent, with the task already escalated to the right audience.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AsanaTasks, projects, milestones — everywhere.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.