Build & Deploy Power Automate Flows with FlowStudio MCP

Step-by-step guide for constructing and deploying Power Automate cloud flows
programmatically through the FlowStudio MCP server.

Prerequisite: A FlowStudio MCP server must be reachable with a valid JWT.
See the power-automate-mcp skill for connection setup.
Subscribe at https://mcp.flowstudio.app

---

Source of Truth

Always call tools/list first to confirm available tool names and their
parameter schemas. Tool names and parameters may change between server versions.
This skill covers response shapes, behavioral notes, and build patterns —
things tools/list cannot tell you. If this document disagrees with tools/list
or a real API response, the API wins.

---

Python Helper

CODEBLOCK0

---

Step 1 — Safety Check: Does the Flow Already Exist?

Always look before you build to avoid duplicates:

CODEBLOCK1

---

Step 2 — Obtain Connection References

Every connector action needs a connectionName that points to a key in the
flow's connectionReferences map. That key links to an authenticated connection
in the environment.

MANDATORY: You MUST call list_live_connections first — do NOT ask the
user for connection names or GUIDs. The API returns the exact values you need.
Only prompt the user if the API confirms that required connections are missing.

2a — Always call list_live_connections first

CODEBLOCK2

2b — Determine which connectors the flow needs

Based on the flow you are building, identify which connectors are required.
Common connector API names:

Connector	API name
SharePoint	INLINECODE8
Outlook / Office 365

shared_office365 |
| Teams | shared_teams |
| Approvals | shared_approvals |
| OneDrive for Business | shared_onedriveforbusiness |
| Excel Online (Business) | shared_excelonlinebusiness |
| Dataverse | shared_commondataserviceforapps |
| Microsoft Forms | shared_microsoftforms |

Flows that need NO connections (e.g. Recurrence + Compose + HTTP only)
can skip the rest of Step 2 — omit connectionReferences from the deploy call.

2c — If connections are missing, guide the user

CODEBLOCK3

2d — Build the connectionReferences block

Only execute this after 2c confirms no missing connectors:

CODEBLOCK4

IMPORTANT — host.connectionName in actions: When building actions in
Step 3, set host.connectionName to the key from this map (e.g.
shared_teams), NOT the connection GUID. The GUID only goes inside the
connectionReferences entry. The engine matches the action's
host.connectionName to the key to find the right connection.

Alternative — if you already have a flow using the same connectors,
you can extract connectionReferences from its definition:
CODEBLOCK5

See the power-automate-mcp skill's connection-references.md reference
for the full connection reference structure.

---

Step 3 — Build the Flow Definition

Construct the definition object. See flow-schema.md
for the full schema and these action pattern references for copy-paste templates:

• - action-patterns-core.md — Variables, control flow, expressions
• action-patterns-data.md — Array transforms, HTTP, parsing
• action-patterns-connectors.md — SharePoint, Outlook, Teams, Approvals

CODEBLOCK6

See build-patterns.md for complete, ready-to-use
flow definitions covering Recurrence+SharePoint+Teams, HTTP triggers, and more.

---

Step 4 — Deploy (Create or Update)

INLINECODE24 handles both creation and updates in a single tool.

Create a new flow (no existing flow)

Omit flowName — the server generates a new GUID and creates via PUT:

CODEBLOCK7

Update an existing flow

Provide flowName to PATCH:

CODEBLOCK8

⚠️ update_live_flow always returns an error key.
null (Python None) means success — do not treat the presence of the key as failure.
⚠️ description is required for both create and update.

Common deployment errors

Error message (contains)	Cause	Fix
INLINECODE32	An action's host.connectionName references a key that doesn't exist in the connectionReferences map	Ensure host.connectionName uses the key from connectionReferences (e.g. shared_teams), not the raw GUID
INLINECODE38 / 403

The connection GUID belongs to another user or is not authorized | Re-run Step 2a and use a connection owned by the current x-api-key user | | InvalidTemplate / InvalidDefinition | Syntax error in the definition JSON | Check runAfter chains, expression syntax, and action type spelling | | ConnectionNotConfigured | A connector action exists but the connection GUID is invalid or expired | Re-check list_live_connections for a fresh GUID |

---

Step 5 — Verify the Deployment

CODEBLOCK9

---

Step 6 — Test the Flow

MANDATORY: Before triggering any test run, ask the user for confirmation.
Running a flow has real side effects — it may send emails, post Teams messages,
write to SharePoint, start approvals, or call external APIs. Explain what the
flow will do and wait for explicit approval before calling trigger_live_flow
or resubmit_live_flow_run.

Updated flows (have prior runs)

The fastest path — resubmit the most recent run:

CODEBLOCK10

Flows already using an HTTP trigger

Fire directly with a test payload:

CODEBLOCK11

Brand-new non-HTTP flows (Recurrence, connector triggers, etc.)

A brand-new Recurrence or connector-triggered flow has no runs to resubmit
and no HTTP endpoint to call. Deploy with a temporary HTTP trigger first,
test the actions, then swap to the production trigger.

7a — Save the real trigger, deploy with a temporary HTTP trigger

CODEBLOCK12

7b — Fire the flow and check the result

CODEBLOCK13

7c — Swap to the production trigger

Once the test run succeeds, replace the temporary HTTP trigger with the real one:

CODEBLOCK14

Why this works: The trigger is just the entry point — the actions are
identical regardless of how the flow starts. Testing via HTTP trigger
exercises all the same Compose, SharePoint, Teams, etc. actions.
Connector triggers (e.g. "When an item is created in SharePoint"):
If actions reference triggerBody() or triggerOutputs(), pass a
representative test payload in trigger_live_flow's body parameter
that matches the shape the connector trigger would produce.

---

Gotchas

Mistake	Consequence	Prevention
Missing connectionReferences in deploy	400 "Supply connectionReferences"	Always call list_live_connections first
INLINECODE53 missing on Foreach

Parallel execution, race conditions on writes | Always add "Sequential" | | union(old_data, new_data) | Old values override new (first-wins) | Use union(new_data, old_data) | | split() on potentially-null string | InvalidTemplate crash | Wrap with coalesce(field, '') | | Checking result["error"] exists | Always present; true error is != null | Use result.get("error") is not None | | Flow deployed but state is "Stopped" | Flow won't run on schedule | Check connection auth; re-enable | | Teams "Chat with Flow bot" recipient as object | 400 GraphUserDetailNotFound | Use plain string with trailing semicolon (see below) |

Teams PostMessageToConversation — Recipient Formats

The body/recipient parameter format depends on the location value:

Location	INLINECODE67 format	Example
Chat with Flow bot	Plain email string with trailing semicolon	INLINECODE68
Channel

Object with groupId and channelId | {"groupId": "...", "channelId": "..."} |

Common mistake: passing {"to": "user@contoso.com"} for "Chat with Flow bot"
returns a 400 GraphUserDetailNotFound error. The API expects a plain string.

---

Reference Files

• - flow-schema.md — Full flow definition JSON schema
• trigger-types.md — Trigger type templates
• action-patterns-core.md — Variables, control flow, expressions
• action-patterns-data.md — Array transforms, HTTP, parsing
• action-patterns-connectors.md — SharePoint, Outlook, Teams, Approvals
• build-patterns.md — Complete flow definition templates (Recurrence+SP+Teams, HTTP trigger)

Related Skills

• - power-automate-mcp — Core connection setup and tool reference
• INLINECODE75 — Debug failing flows after deployment