flowstudio-power-automate-build

What it does

Guides an agent to construct, wire, deploy, verify, and test Power Automate cloud flows through the FlowStudio MCP server. It supports creating new flows or updating existing ones, building a flow definition, resolving connection references, deploying via update_live_flow, and performing post-deploy verification and testing steps. The workflow emphasizes using MCP calls like list_live_flows, get_live_flow, update_live_flow, get_live_flow, resubmit_live_flow_run, trigger_live_flow, get_live_flow_runs, and related describe-assisted steps to define connectors and actions, all without opening the portal.

How it works

• Load the current build tools by calling tool_search with query "skill:create-flow" for new flows or using the build-flow bundle for edits.
• Check if the flow already exists with list_live_flows and derive FLOW_ID if found; otherwise proceed with a blank new flow.
• Obtain active connections via list_live_connections, confirm required connectors exist, and build connection_references and host_templates blocks for the flow.
• Build the flow definition object with the required schema, including triggers and actions, informed by live connector descriptors when possible.
• Deploy the flow with update_live_flow; omit flowName for creation, or include flowName for updates; set a displayName and description accordingly.
• Verify deployment by calling get_live_flow and inspecting properties.state and the actions present in the definition.
• Test the flow using resubmit_live_flow_run for existing flows or trigger_live_flow for new, non-HTTP scenarios, ensuring user confirmation before triggering tests.

When to use it

Use when asked to create a flow, build a new flow, deploy a flow definition, scaffold a Power Automate workflow, construct a flow JSON, update an existing flow's actions, patch a flow definition, add actions to a flow, wire up connections, or generate a workflow definition from scratch. Requires a FlowStudio MCP subscription.

What it can touch

• Tools: copilot (as declared)
• MCP API via Python helper code blocks in the skill for calling: tool_search, list_live_flows, get_live_flow, list_live_connections, describe_live_connector, get_live_dynamic_options, update_live_flow, get_live_flow_runs, resubmit_live_flow_run, trigger_live_flow, set_live_flow_state, get_live_flow_runs, get_live_flow_run_error, and related auxiliary tools described in the instructions.

Caveats

• Requires a FlowStudio MCP subscription.
• The skill emphasizes calling list_skills / tool_search first to confirm available tool names and parameter schemas and notes that tool schemas may change between server versions.
• The update_live_flow tool returns an error key on failure; a missing key value indicates success. Do not treat the presence of the error key as failure when its value is null.
• Flow description is in definition["description"], and the server may append "#flowstudio-mcp" for usage tracking; do not pass a top-level description argument unless the active schema shows one.
• Testing requires explicit user confirmation before triggering actions that have real side effects (emails, Teams messages, etc.).