Asana Milestone to Stakeholder Comms

Overview

FlowLibs - Asana Milestone to Stakeholder Comms keeps project stakeholders informed when key Asana milestones are reached. On a daily schedule it scans an Asana project for milestone-marked tasks that completed inside a recency window, posts a confirmation comment back onto each milestone task in Asana, emails the stakeholder distribution list, and posts a celebratory roll-up to the project's Microsoft Teams channel.

Why it matters: Stakeholders care about milestones, not every task. Automatic, well-framed milestone comms keep them informed at the moments that matter and build momentum - without the PM having to remember to send the update.

Status: Built and shipped Off (demo). Going live requires only authorizing the three connections and setting the environment-variable values.

Use Case

A project manager wants stakeholders updated automatically the moment a key milestone is hit, without manually composing an announcement each time. Milestones are flagged in Asana by a naming-convention marker (e.g. a task named [Milestone] Phase 1 sign-off). When such a task is completed, the flow fans out the news to email and Teams and leaves an audit comment on the milestone task itself.

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.

Trigger cadence

Adjust the Recurrence frequency and set flowlibs_MilestoneLookbackHours to match (e.g. hourly poll with a 1-hour window for near-real-time comms).

Milestone definition

Change flowlibs_MilestoneMarker to whatever naming convention the team uses, or swap the filter to read an Asana custom field / tag if you add an HTTP enrichment step.

Add a status page

Insert a SharePoint UpdateItem (or Word/PDF generation) in the loop to update a project status page, restoring the original idea's SharePoint step.

Audience tiering

Send an exec summary email and a detailed PM email by splitting Email_Stakeholders into two actions with different recipient env vars.

What's next / unblocks

Enrich the email body by reading dependent tasks via the Asana REST API and listing what the milestone unblocks.

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.

@{addHours(utcNow(), mul(-1, int(variables('varLookbackHours'))))}

@and(equals(item()?['completed'], true), and(contains(coalesce(item()?['name'], ''), variables('varMilestoneMarker')), greater(coalesce(item()?['completed_at'], '1900-01-01T00:00:00.000Z'), variables('varCutoffUtc'))))

@{concat('Milestone reached: "', items('For_Each_Milestone')?['name'], '". Stakeholders have been notified by email and the project Teams channel.')}

@greater(variables('varMilestoneCount'), 0)

Customize & download