Trello High-Priority Card to Teams War Room

Overview

This flow bridges Trello triage to Microsoft Teams coordination with a full incident lifecycle backed by Dataverse. On a 15-minute schedule it reads the board, detects cards carrying the configured urgent/incident label, opens a Teams war-room thread, writes the thread link back onto the card as a comment, and logs the incident to a Dataverse table. On a later run, when a logged incident's card has moved to Done, it posts a resolution note and closes the Dataverse record.

Why it matters: triage happens on the board, but coordination happens in Teams. This bridges them automatically and keeps a clean system-of-record in Dataverse - without anyone re-keying anything.

Ships Off; turn on by authorizing the three connections and setting the env vars.

Use Case

Operations / IT teams that triage incidents on a Trello board want urgent cards to instantly spin up a Teams coordination thread, surface that thread back on the card for triagers, and maintain an auditable incident log - with automatic resolution tracking when the work is done.

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.

Polling cadence

Change the recurrence to match your urgency SLA (e.g. every 5 minutes for high-severity boards).

Per-incident channel

Swap the war-room post to create a dedicated channel per major incident instead of one shared channel.

Escalation / paging

Chain a PagerDuty or Twilio action after Log Incident to page on-call for after-hours urgent cards.

Multiple urgent labels

Change the filter to test membership against an array of label ids (urgent + incident).

Stale-incident cadence

Add a branch that re-pings the channel for incidents open longer than N hours.

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(equals(item()?['closed'], false), contains(coalesce(item()?['idLabels'], createArray()), variables('varUrgentLabelId')))

equals(length(body('Lookup_Existing_Incident')?['value']), 0)

coalesce(body('Post_War_Room_Thread')?['messageLink'], concat('https://teams.microsoft.com/l/channel/', variables('varTeamsChannelId'), '/War%20Room'))

and(greater(length(body('Match_Card_On_Board')), 0), equals(first(body('Match_Card_On_Board'))?['idList'], variables('varDoneListId')))

utcNow()