monday.com Form Intake to Board

Overview

This flow turns inbound Microsoft Form requests into structured monday.com board items. When a new form response is submitted, the flow reads the answers, creates a board item (with mapped column values) in the target group, builds a link to the new item, and emails the requester a confirmation. It ships Off as a portable demo — going live requires only authorizing the three connections and setting the environment-variable values.

Why it matters: Requests that arrive by form or email get lost; structured board items are trackable and assignable. Automating intake removes manual re-entry and speeds first response.

Status: Built · Flow Checker 0 errors / 0 warnings · State = Off (demo)

Use Case

A team that runs its work on monday.com wants form-based requests captured as board items automatically, with the requester acknowledged immediately and a deep link back to the created item.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Microsoft Forms	shared_microsoftforms	CreateFormWebhook GetFormResponseById
monday.com	shared_mondaycom	InvokeMondayMCP
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.

Map answers to columns

Set flowlibs_MondayColumnValuesJson to a monday column_values object (e.g. {"status":{"label":"New"},"text":"..."}). To map specific answers, reference the form answer fields from Get response details inside Build GraphQL Mutation.

Item title

Edit Compose ItemName to use a specific answer (e.g. a Subject question) instead of the responder + timestamp.

Routing

Drive flowlibs_MondayBoardId / flowlibs_MondayGroupId from a request-type answer to route different requests to different boards or groups.

Attachments

The MCP connector does not expose a file-upload op; to upload form attachments to a file column, add an HTTP step to the monday.com /v2/file endpoint (multipart) as a follow-on.

Owner / SLA

Add a people column id and a date column id to the column-values payload to auto-assign an owner or due date.

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.

@triggerOutputs()?['body/resourceData/responseId']

@coalesce(body('Get_response_details')?['responder'], variables('varFallbackEmail'))

@{concat('mutation { create_item (board_id: ', variables('varBoardId'), ', group_id: "', variables('varGroupId'), '", item_name: "', ..., '", column_values: "', replace(variables('varColumnValues'),'"','\"'), '") { id name } }')}

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

@{coalesce(json(coalesce(body('Create_Item')?['result']?['content']?[0]?['text'],'{}'))?['data']?['create_item']?['id'],'')}

@{concat('https://', variables('varAccountSlug'), '.monday.com/boards/', variables('varBoardId'), '/pulses/', outputs('Compose_ItemId'))}

Customize & download