monday.com Sprint and Workload Digest

Overview

This flow produces an automatic daily standup digest from a monday.com board. Each morning before standup it reads the board through the monday.com MCP connector, builds an HTML summary of every item (name, group/sprint, status), posts that digest to a Teams standup channel, and emails the same breakdown to a configured recipient.

Why it matters: Standup prep is repetitive manual work. An automatic board readout gives the team a shared picture each morning so the meeting can focus on blockers instead of status collection.

Status: Built and verified — Flow Checker 0 errors / 0 warnings. Ships Off (demo). Going live requires only authorizing the three connections and setting the environment variable values.

Use Case

A team running sprints on monday.com wants a consistent morning standup summary delivered to Teams (and email) without anyone compiling it by hand. The flow runs on a daily schedule and reads the board live, so the digest always reflects the current board state.

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.

Per-owner DM / email split

Instead of one digest email, group items by the People column and send each owner only their items (loop the owners, filter the rows).

Sprint burndown

Add a chart or count of items completed yesterday vs. remaining, by pulling the board's date/status history.

Blocked-item focus

Add a Filter/Condition on the status text to surface only Blocked / Stuck items at the top of the digest.

Adaptive Card

Replace the HTML table Teams post with an Adaptive Card for richer formatting and per-item action buttons.

Weekdays only

Change the Recurrence to a weekday schedule so it skips weekends.

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'), ']) { name items_page(limit: 200) { items { id name group { title } column_values(ids: ["', variables('varStatusColumnId'), '"]) { id text } } } } }')

coalesce(outputs('Init_Session')?['headers']?['Mcp-Session-Id'],'')

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

length(outputs('Get_Items'))

coalesce(first(item()?['column_values'])?['text'],'No status')

Customize & download