monday.com Deadline and Overdue Escalation

Overview

This flow enforces deadlines on monday.com. On a daily schedule it scans a monday.com board for items that are due today or overdue (by a configured date column), posts a reminder for each one into a Microsoft Teams channel, and escalates any item overdue past a configurable threshold to the board owner — both by posting a comment/update directly onto the monday.com item and by emailing the board owner.

Why it matters: monday.com's built-in reminders are easy to miss. Consolidated, escalating deadline management keeps delivery work on schedule without manual chasing.

Status: Built — ships Off (demo). Going live requires only authorizing the three connections and setting the environment-variable values.

Use Case

A delivery team running its work on a monday.com board wants automatic deadline chasing and escalation. Each morning the flow nudges the team about anything due or overdue, and for items that have slipped past the tolerance window it pulls in the board owner with an on-item comment plus an email — creating a visible, auditable escalation trail.

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-board / multi-board

Loop over several board ids by storing a comma-separated list and splitting it, or duplicate the query block per board.

Status-aware

Extend the GraphQL query to also pull the status column and skip items already marked Done in Filter Due Overdue.

De-dupe escalations

Add a Dataverse (or monday column) ledger keyed by item id so an item is escalated only once, not every daily run.

Assignee mention

Query the people column and resolve assignees to Teams mentions for a more targeted nudge.

Schedule

Change the Daily 0800 recurrence (frequency, time, time zone) to fit the team's working 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.

concat('query { boards(ids: [', parameters('EnvVar_MondayBoardId'), ']) { items_page(limit: 100) { items { id name column_values(ids: ["', parameters('EnvVar_DateColumnId'), '"]) { id text value } } } } }')

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

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

and(not(empty(first(item()?['column_values'])?['text'])), lessOrEquals(first(item()?['column_values'])?['text'], variables('varTodayDate')))

div(sub(ticks(utcNow()), ticks(concat(outputs('Compose_DueDate'),'T00:00:00Z'))), 864000000000)

concat('mutation { create_update (item_id: ', items('Apply_to_each_Due_Item')?['id'], ', body: "', variables('varEscalationText'), ' ... ") { id } }')

Customize & download