Asana Blocked Dependency Alert

Overview

This flow surfaces blocked work in Asana before it stalls a delivery. On a daily schedule it sweeps every monitored Asana project, finds incomplete tasks that are blocked by an incomplete dependency or carry a Blocked tag, posts a comment on the blocked task documenting the blocker, notifies the project channel in Microsoft Teams, and escalates any blocker that sits on the critical path by email to the manager.

Why it matters: Blocked tasks stall silently — the blocked assignee waits, and the owner of the blocking task often doesn't even know they're holding up downstream work. Surfacing the dependency to both parties fast, with an audit comment on the task itself, keeps work flowing.

Status: Built and shipped Off (demo). Going live requires only authorizing the three connections + setting the environment-variable values (Asana workspace/project GIDs, Teams group/channel, manager email, and the Asana PAT in Key Vault).

Use Case

A delivery team runs its work in Asana with task dependencies. They want dependency blockers detected automatically each morning and routed to the people who can clear them — the blocked task's assignee and the channel owner — with critical-path blockers escalated to management. The flow also leaves a comment on the Asana task so the blocker is documented in-context.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Asana	shared_asana	ListTasks AddComment
Microsoft Teams	shared_teams	PostMessageToConversation
Office 365 Outlook	shared_office365	SendEmailV2
HHTTP	http	GET /tasks/{id} (dependency/tag lookup)

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Predicted slip

Extend the comment/Teams message to estimate downstream delay from the blocker's own due date.

Per-project digest

Collect blocked tasks into an array and send one rolled-up Teams card per project instead of one message per task.

Trigger on task update

Swap the Recurrence trigger for an Asana task-updated trigger to surface blockers in near real-time (keep the same body of logic).

Tune the Blocked marker

Change varBlockedTagMarker to match your board's tag (e.g. on-hold).

Wider escalation

Add a second critical tier or CC the blocking task's owner on the escalation email.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@split(variables('varAsanaProjectIds'), ',')

@equals(item()?['completed'], false)

@{concat(variables('varAsanaApiBase'), '/tasks/', string(items('For_Each_Open_Task')?['id']), '?opt_fields=name,permalink_url,due_on,assignee.name,assignee.email,tags.name,dependencies.name,dependencies.gid,dependencies.completed')}

@equals(item()?['completed'], false)

@or(greater(outputs('Compose_Incomplete_Dep_Count'), 0), equals(outputs('Compose_Is_Marked_Blocked'), true))

@contains(toLower(string(coalesce(body('Get_Task_Dependencies')?['data']?['tags'], createArray()))), toLower(variables('varCriticalTag')))

Customize & download