Trello WIP Limit Enforcer

Overview

This flow enforces Work-In-Progress (WIP) limits on a Trello board. On a schedule it reads every list and open card, counts cards per list against a configurable per-list limit, and when a list exceeds its limit it flags the newest card with a comment, posts a consolidated WIP-breach alert to a Microsoft Teams channel, and emails the team lead a summary.

Why it matters: WIP limits are the core discipline of Kanban - they force teams to finish work before starting new work. Trello has no native WIP enforcement, so limits get ignored. This surfaces overload automatically and nudges the team to pull rather than push.

Ships Off - turn on after authorizing connections and setting the board ID and limits.

Use Case

A team running Kanban on a Trello board wants its WIP limits actually respected. Instead of relying on people to self-police, a scheduled check counts cards per list and raises an alert the moment a list goes over its limit - flagging the newest card, notifying the channel, and emailing the lead.

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.

Tune limits without editing logic

Change flowlibs_WipLimitMap (per-list) or flowlibs_DefaultWipLimit (catch-all). No flow edits needed.

Change cadence

Edit the Check WIP Limits recurrence (e.g. every 15 min during work hours, or daily).

Block on breach

Add a red label to all cards in an over-limit list via UpdateCard_V2 idLabels inside the loop, not just a comment on the newest.

Aging WIP

Add a second check to flag cards sitting in a list past an age threshold using dateLastActivity.

Trend reporting

Log each breach (list, count, limit, timestamp) to a Dataverse table or SharePoint list to spot chronic bottlenecks.

Per-list owners

Replace the single flowlibs_LeadEmail with a name to email map and notify the specific list owner.

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.

int(coalesce(json(variables('varWipMap'))?[items('Apply_to_each_List')?['name']], variables('varDefaultLimit')))

and(equals(item()?['idList'], items('Apply_to_each_List')?['id']), equals(item()?['closed'], false))

greater(outputs('Compose_List_Count'), outputs('Compose_List_Limit'))

last(sort(body('Filter_Cards_In_List'), 'dateLastActivity'))

greater(variables('varBreachCount'), 0)