Asana to Microsoft Planner Two-Way Sync

Overview

Bidirectionally syncs an Asana project with a Microsoft Planner plan. Asana is authoritative for task content (title, due date) and pushes create/update into Planner; completion status is bidirectional. A Dataverse ID-map table links each Asana task to its mirrored Planner task and carries a last-source flag plus per-side completion flags so completions never ping-pong between the two systems.

Why it matters: Some team members live in Asana, others in Teams/Planner. A loop-safe two-way sync means neither side has to switch tools, and both see the same task list and completion state.

Built as one solution with two cloud flows + one Dataverse table (Asana Planner Task Map). Both flows ship Off.

Use Case

A team split across Asana and Planner wants tasks and completion mirrored across both tools, without duplicate tasks or infinite update loops.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Asana	shared_asana	ListTasks CompleteTaskV2 AddComment
Microsoft Planner	shared_planner	CreateTask_V3 UpdateTask_V2 ListTasks_V3
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord UpdateRecord
Microsoft Teams

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.

Section to bucket routing

Extend flowlibs_BucketMap with one key per Asana section to route tasks into matching Planner buckets (Asana ListTasks doesn't return section, so resolving section requires an Asana REST call).

Assignee map

Map Asana people to Planner/AAD users (Planner CreateTask_V3 accepts body/assignments).

Sync cadence

Adjust the Recurrence interval on both flows (default 15 min). Keep both equal to minimise drift.

Richer content writeback

To push Planner title/notes/due back to Asana, add a built-in HTTP PUT https://app.asana.com/api/1.0/tasks/{id} (Asana connector has no general update op) with a Key Vault-backed PAT.

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.

@coalesce(json(variables('varBucketMap'))?['default'], variables('varPlannerBucketId'))

@if(equals(items('Apply_To_Each_Asana_Task')?['completed'], true), '100', '0')

@concat('flowlibs_asanataskid eq ''', string(items('Apply_To_Each_Asana_Task')?['id']), '''')

AND( length(value) > 0, string(percentComplete) = '100', flowlibs_asanacompleted = 'false' )

@guid()

Customize & download