monday.com Time Tracking to Billing

Overview

This flow turns monday.com tracked time into draft invoices. On a monthly schedule it reads logged time from a time-tracking column across one or more client boards (via the monday.com MCP connector running GraphQL), aggregates billable hours by client/project, applies a configurable rate map, creates a Draft Invoice record in Dataverse per client/project, and emails a consolidated billing summary to finance.

Why it matters: Compiling billable time by hand is slow and error-prone. Automating the aggregation and draft-invoice creation speeds the billing cycle and reduces revenue leakage, while keeping a human review gate (invoices land as Draft).

Status: Built and published in the default environment. Ships Off (demo) — going live requires only authorizing the three connections and setting the environment variable values.

Use Case

A services firm tracks billable time in monday.com client boards and wants periodic, automatically-compiled draft invoices for finance to review and finalize, rather than manually tallying hours each month.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
monday.com	shared_mondaycom	InvokeMondayMCP
Microsoft Dataverse	shared_commondataserviceforapps	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 Dataverse CreateRecord with the accounting connector to create invoices directly in the billing system.

Approval gate

Add an Approvals action before finalizing so finance approves draft invoices.

Billable vs internal

Add a status/billable column filter in the GraphQL query or a Filter array to exclude non-billable time.

Rate by role

Extend the Rate Map JSON to key on client+role and read a role column from monday.

Time parsing

Compose Billable Hours reads the column text as a number; adjust the expression if your time column stores a duration string (e.g. HH:MM:SS).

Schedule

Change the Recurrence frequency/interval for weekly or bi-weekly billing.

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

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

coalesce(float(first(items('Apply_to_each_Time_Entry')?['time'])?['text']),0)

coalesce(json(variables('varRateMap'))?[outputs('Compose_Client_Name')],json(variables('varRateMap'))?['default'],0)

mul(float(outputs('Compose_Billable_Hours')),float(outputs('Compose_Hourly_Rate')))

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

Customize & download