Trello Dev Card to Azure DevOps Work Item

Overview

This solution bridges a Trello board with Azure DevOps, with Microsoft Teams alerts and a Dataverse cross-reference table as the system of record. When a Trello card is flagged for engineering, the producer flow creates a linked Azure DevOps work item, comments the work-item link back onto the card, logs the link in Dataverse, and alerts the dev channel in Teams. A second flow mirrors Azure DevOps state changes back onto the Trello card by moving it between lists.

Why it matters: stakeholders triage in Trello; engineers work in the Azure DevOps backlog. A loop-guarded two-way sync keeps both honest without duplicate data entry.

Built as two scheduled-poll flows plus one Dataverse table; both ship Off. The Azure DevOps connector has no dedicated work-item operation, so the connector's own HttpRequest action is used (json-patch create + REST get).

Use Case

A product team triages incoming work in Trello but development happens in Azure DevOps. They want engineering-flagged cards reflected as work items automatically, with status kept in step between the two tools and the dev channel notified when new work lands.

Flow Architecture

Environment Variables

Connectors & Connections

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.

Cadence

Both flows poll every 15 minutes; adjust the Recurrence for tighter or looser sync.

Work item type & fields

Change flowlibs_AdoWorkItemType, or extend Compose Work Item Patch to set Area Path, Iteration, Assigned To, or Tags from card data.

State mapping

Edit flowlibs_AdoStateToListMap to match your board's list ids and your team's ADO states.

Dedup

Handled by the Lookup Existing Link Dataverse check; no duplicate work items are created for a card that already has a link row.

Two-way comment sync

Extend the sync-back with an ADO comment read and a Trello AddCommentToCard to mirror engineering comments back to triagers.

Label resolution

flowlibs_DevLabelId expects the Trello label id (not name); read it from the board JSON or a card's idLabels.

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(contains(coalesce(item()?['idLabels'], json('[]')), variables('varDevLabelId')), not(item()?['closed']))

equals(length(outputs('Lookup_Existing_Link')?['body/value']), 0)

concat(variables('varAdoProject'), '/_apis/wit/workitems/$', variables('varWorkItemType'), '?api-version=7.0')

not(equals(outputs('Compose_New_State'), items('For_Each_Link')?['flowlibs_adostate']))

json(variables('varStateMap'))?[outputs('Compose_New_State')]