monday.com WIP and Capacity Guard

Overview

FlowLibs - monday.com WIP and Capacity Guard is a scheduled cloud flow that protects against work-in-progress (WIP) overload. Once a day it reads every item on a configured monday.com board, counts how many in-progress items each owner holds, and when any owner exceeds the configured WIP limit it posts an alert to a Microsoft Teams channel and emails the manager a rebalancing suggestion.

Why it matters: Overloaded people drop balls and burn out. Surfacing capacity breaches early keeps WIP healthy and prompts rebalancing before delivery slips.

Status: Built and published to the default environment in the Off state. Going live requires only authorizing the three connections and setting the environment variable values — no logic changes.

Use Case

A delivery team manages work on a monday.com board with a status column and a people (owner) column. Leadership wants an automatic, daily early-warning when an individual is carrying more in-progress items than the agreed WIP limit, so work can be rebalanced before it stalls.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
monday.com	shared_mondaycom	InvokeMondayMCP
Microsoft Teams	shared_teams	PostMessageToConversation
Office 365 Outlook	shared_office365	SendEmailV2

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.

Tighten or relax the limit

Change flowlibs_WipCapacityLimit. For per-owner limits, replace the single limit with a JSON map env var and look up the current owner's limit in the condition.

Change the cadence

Edit the Recurrence trigger (e.g. hourly, or weekdays only).

Notify the owner directly

Add an Office 365 Users lookup to resolve the owner's email from their monday.com display name, then email them as well as the manager.

Effort-weighted WIP

Pull an effort/size column in the GraphQL query and sum it instead of counting items.

Adaptive Card

Replace the HTML Teams message with an Adaptive Card that includes the over-capacity item list.

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.

@{concat('query { boards(ids: [', variables('varBoardId'), ']) { items_page(limit: 200) { items { id name status: column_values(ids: ["', variables('varStatusColumnId'), '"]) { text } owner: column_values(ids: ["', variables('varOwnerColumnId'), '"]) { text } } } } }')}

@{coalesce(outputs('Init_Monday_Session')?['headers']?['Mcp-Session-Id'],'')}

@coalesce(json(coalesce(body('Query_Board_Items')?['result']?['content']?[0]?['text'],'{}'))?['data']?['boards']?[0]?['items_page']?['items'], json('[]'))

@coalesce(first(item()?['owner'])?['text'],'Unassigned')

@equals(toLower(trim(coalesce(item()?['Status'],''))), toLower(trim(variables('varInProgressLabel'))))

greater( length(body('Filter_Owner_In_Progress_Items')), variables('varCapacityLimit') )

Customize & download