monday.com Status Change to CRM/ERP Action

Overview

This flow connects monday.com workflows to systems of record. When an item's status changes on a monitored board (e.g. to Ready to Invoice, Shipped, Approved), the flow performs the matching downstream action — create an invoice/CRM record in Dataverse, or notify a customer via Outlook — and writes a result reference back onto the monday.com item. It is idempotent: a Dataverse ledger guarantees a re-fired status does not double-act.

Why it matters: monday.com is great for process, but the value lands when status changes drive real actions in finance/CRM systems instead of manual re-entry.

Build status: Built and verified in this org (Off/demo). Flow Checker 0 errors / 0 warnings.

Build Note — Trigger Adaptation: The monday.com connector (shared_mondaycom) is an MCP-invoke connector (single InvokeMondayMCP over JSON-RPC + GraphQL). It has no native when-status-changes trigger. The flow uses a Recurrence poll (every 15 minutes) that reads the board via GraphQL and detects status changes against a Dataverse idempotency ledger (flowlibs_mondaystatusaction) — the connector-first equivalent of the status-change trigger.

Use Case

A team that runs a process on monday.com wants status changes to drive the corresponding action in the system of record — invoicing, CRM updates, or customer comms — automatically and without double-processing.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
monday.com	shared_mondaycom	InvokeMondayMCP
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord
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.

QuickBooks/Xero

Replace the Invoice-case Dataverse write with the finance system's create-invoice action.

Real CRM

Point the UpdateCRM-case Dataverse write at your CRM deal table.

Customer comms

Extend the Notify case (Shipped/Delivered) with templated emails or Teams.

Approval gate

Insert an Approvals action before high-value actions (e.g. large invoices).

Poll cadence

Adjust the Recurrence interval, or swap to a webhook if monday.com webhooks are wired to an HTTP-trigger receiver flow.

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: 100) { items { id name statuscol: column_values(ids: ["', variables('varStatusColumnId'), '"]) { text } } } } }')

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

coalesce(first(item()?['statuscol'])?['text'],'')

coalesce(json(variables('varStatusActionMap'))?[outputs('Compose_ItemStatus')],'')

flowlibs_mondayitemid eq '{id}' and flowlibs_status eq '{status}'

concat('mutation { change_simple_column_value(board_id: ', variables('varBoardId'), ', item_id: ', string(item()?['id']), ', column_id: "', variables('varResultColumnId'), '", value: "', variables('varResultRef'), '") { id } }')

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

Customize & download