Notion Tasks to Microsoft Planner Sync

Overview

This solution keeps a Notion tasks database in two-way sync with a Microsoft Planner plan. New/changed Notion tasks create or update Planner tasks in the mapped bucket; when a Planner task is completed, the status is written back to the matching Notion page. A Dataverse ID-mapping ledger plus a source flag prevent infinite update loops, so a Notion-first team and a Planner/Teams team can work from one shared list.

Why it matters: Some people live in Notion, others in Planner/Teams. A loop-safe bidirectional sync means neither group has to switch tools or duplicate effort.

> Built as a two-flow + one-table solution (FlowLibs build CF-449). Ships Off — going live needs only connection authorization and environment-variable values.

Use Case

A team plans in Notion but executes in Teams/Planner (or vice versa). They want tasks and completion status mirrored across both tools, with status-to-bucket mapping and no infinite echo loops.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Notion (Independent Publisher)	shared_notionip	Query_a_database
Microsoft Planner	shared_planner	CreateTask_V3 UpdateTask_V2 OnCompleteTask
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.

Bucket mapping

Populate flowlibs_PlannerBucketMap with {"<Notion status>":"<Planner bucket id>"} pairs to route tasks into buckets.

Status property type

The Notion status read coalesces Status- and Select-type properties; the writeback PATCH targets a Status property. If your DB uses a Select, change the PATCH body from status to select.

Completion mapping

percentComplete is set to 100 when the Notion status equals flowlibs_NotionStatusDoneValue, else 0. Extend with a richer status to percent map if needed.

Assignees / due dates / labels

Extend CreateTask_V3/UpdateTask_V2 with assignments, dueDateTime, and appliedCategories and map from Notion properties.

Polling cadence

Adjust the Recurrence interval on Flow A and the Planner OnCompleteTask poll on Flow B.

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(items('Apply_to_each_Notion_Task')?['properties']?[parameters('EnvVar_NotionStatusPropertyName')]?['status']?['name'], items('Apply_to_each_Notion_Task')?['properties']?[parameters('EnvVar_NotionStatusPropertyName')]?['select']?['name'], '')}

@{coalesce(first(items('Apply_to_each_Notion_Task')?['properties']?[parameters('EnvVar_NotionTitlePropertyName')]?['title'])?['plain_text'], 'Untitled Notion Task')}

@{coalesce(json(parameters('EnvVar_PlannerBucketMap'))?[outputs('Compose_Notion_Status')], '')}

@and(greater(length(body('List_Mapping_By_Planner_Task')?['value']),0), not(equals(coalesce(first(...)?['flowlibs_lastsyncedstatus'],''), parameters('EnvVar_NotionStatusDoneValue'))))

@json(concat('{"properties":{"', parameters('EnvVar_NotionStatusPropertyName'), '":{"status":{"name":"', parameters('EnvVar_NotionStatusDoneValue'), '"}}}}'))

Customize & download