Notion Bug Tracker to Azure DevOps Sync

Overview

This solution keeps a Notion bug database and Azure DevOps in two-way sync and notifies a Microsoft Teams dev channel. Non-developers triage bugs in Notion; engineers work the matching work items in Azure DevOps; state and priority stay aligned in both directions without duplicate data entry.

Because the Notion connector has no trigger and Azure DevOps changes are reconciled on a schedule, the sync is implemented as two poll-based cloud flows + one Dataverse mapping/ledger table. Echo loops are prevented by comparing each side's current value against the last-synced value stored in the ledger (a per-row idempotency check), backed by a source flag for audit.

Both flows ship Off (demo) with Flow Checker 0 errors / 0 warnings.

Use Case

A product team logs and triages incoming bugs in a Notion database, but engineering works in Azure DevOps. They want every Notion bug reflected as an ADO work item, status/priority kept in step in both directions, the linkage recorded so updates target the right counterpart, and the dev channel notified on new and changed bugs.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Notion	shared_notionip	Query_a_database
Azure DevOps	shared_visualstudioteamservices	HttpRequest
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord UpdateRecord
Microsoft Teams	shared_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.

Connect & configure

Authorize the four connections, then set the env var values (Notion DB id + integration secret, ADO org/project, Teams group/channel ids).

Map your Notion schema

Point the flowlibs_NotionBug*Prop env vars at your actual property names; state/priority extraction supports both Notion status and select types.

State mapping

Notion state text is copied to ADO System.Tags and ADO System.State is copied back to the Notion status property. For strict workflows, insert a state-mapping Compose/Switch.

Priority mapping

Priority is carried as an ADO tag. To set the real Microsoft.VSTS.Common.Priority (1-4), add a mapping step in Compose_New/Update_Work_Item_Patch.

Cadence

Adjust the two Recurrence triggers (default 15 min) to your SLA.

Turn on

Flip both flows On once connections and env vars are set.

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_Bug')?['properties']?[parameters('EnvVar_NotionBugStateProp')]?['status']?['name'], items('Apply_To_Each_Bug')?['properties']?[parameters('EnvVar_NotionBugStateProp')]?['select']?['name'], 'New')

@or(not(equals(outputs('Compose_Existing_Mapping')?['flowlibs_laststate'], outputs('Compose_Bug_Fields')?['state'])), not(equals(outputs('Compose_Existing_Mapping')?['flowlibs_lastpriority'], outputs('Compose_Bug_Fields')?['priority'])))

@{concat(parameters('EnvVar_AdoProject'),'/_apis/wit/workitems/$',parameters('EnvVar_AdoBugWorkItemType'),'?api-version=',parameters('EnvVar_AdoApiVersion'))}

{ "op":"add", "path":"/fields/System.History", "value":"Synced from Notion bug tracker" }

@json(concat('{"properties":{"', parameters('EnvVar_NotionBugStateProp'), '":{"status":{"name":"', outputs('Compose_Work_Item_Fields')?['state'], '"}}}}'))

SELECT [System.Id] FROM WorkItems WHERE [System.Tags] CONTAINS 'NotionSync' AND [System.ChangedDate] >= @Today-1 ORDER BY [System.ChangedDate] DESC

Customize & download