Asana Task Deadline Escalation

Overview

This flow enforces deadlines on Asana tasks. Every morning it queries a monitored Asana project for tasks that are due today or overdue, posts a per-task reminder into a Microsoft Teams channel, escalates any task overdue beyond a configurable threshold by adding a comment directly on the Asana task, and emails the project owner a consolidated digest of all at-risk and overdue work.

Why it matters: Asana sends individual reminders but no single, escalating, owner-facing view of deadline risk. This flow delivers a daily picture to the owner and nudges assignees where they already work (Teams), while flagging genuinely stale items in Asana itself.

Status: Built and deployed Off (demo). Going live requires only authorizing the three connections and setting the six environment-variable values — no logic changes.

Use Case

A delivery team runs work in Asana and wants automatic daily deadline chasing — assignee nudges, an owner digest, and escalation on stale overdue tasks — without a manual standup review. Project Managers and Operations get a reliable morning sweep that keeps delivery on track.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Asana	shared_asana	ListTasks AddComment
Office 365 Outlook	shared_office365	SendEmailV2
Microsoft Teams	shared_teams	PostMessageToConversation

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.

Custom fields

Use an Asana custom field (priority/risk) to weight which tasks escalate first, or to filter the loop.

Section scope

Limit to specific sections (e.g. "In Progress") to avoid nagging backlog items.

Per-assignee Teams DM

Map the Asana assignee to a Teams user and post a 1:1 chat instead of a channel message.

Portfolio view

Loop multiple projects (store a comma-separated list of project gids) for a program-level digest.

Idempotent escalation

Add a small Dataverse ledger to avoid re-commenting on the same task every day.

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.

@and(equals(item()?['completed'], false), and(not(equals(coalesce(item()?['due_on'],''),'')), lessOrEquals(coalesce(item()?['due_on'],'9999-12-31'), variables('varToday'))))

@div(sub(ticks(utcNow()), ticks(items('Apply_To_Each_Task')?['due_on'])), 864000000000)

@coalesce(items('Apply_To_Each_Task')?['assignee']?['name'], 'Unassigned')

greater(<days overdue>, variables('varOverdueDays'))

Customize & download