Skip to main content
skill CX Codex

build-flow · microsoft — Claude Code skill for Power Automate flows

build-flow turns a written request into a Power Automate flow, checks its definition, then creates it. Use it when you want an agent to assemble a flow from a description.

MIT ★ 1,167 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add microsoft/power-platform-skills
/plugin install power-automate@power-platform-skills
Open on GitHub

What build-flow does

Describe the automation you need. The skill discovers an environment and its connections, builds a complete Power Automate flow definition, and creates the flow. It checks connections and validates the definition first; publishing can follow creation. For connector actions, it looks up the operation’s exact parameters and action type rather than guessing.

The skill works through FlowAgent MCP tools. Standard connector operations use OpenApiConnection; webhook operations use OpenApiConnectionWebhook. It does not put authentication in action inputs. HTTP triggers require Premium, so Button is the option for free or seeded plans. Validation is mandatory because the API rejects invalid definitions. If a connection is missing or not Connected, the build stops.

What it helps with

  • build a Power Automate flow from a written request
  • find an environment and check its connections
  • look up exact connector operation parameters
  • validate a flow definition before creation
  • publish a newly created flow

Example prompts for the agent

  • Create a flow that sends a Teams notification when a row is added to a table.
  • Build a flow for new requests and check the SharePoint connection before creating it.
  • Create a manually triggered Power Automate flow and publish it after validation.

How to install build-flow

1Plugin marketplace

/plugin marketplace add microsoft/power-platform-skills
/plugin install power-automate@power-platform-skills

This installs the whole power-automate plugin with all its skills

2Skills CLI (Vercel)

npx skills add microsoft/power-platform-skills --skill build-flow -a claude-code

3Manually: put the files in place

~/.claude/skills/build-flow/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/build-flow/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about build-flow

How do I install build-flow in Claude Code?

Run these commands in order: /plugin marketplace add microsoft/power-platform-skills, then /plugin install power-automate@power-platform-skills.

What does build-flow do?

It turns a description into a Power Automate flow definition, checks connections, validates the definition, and creates the flow. It can publish the result afterward.

Can it skip validation or use an HTTP trigger without Premium?

No. Validation is required, and HTTP triggers require Premium. Button is the trigger option for free or seeded plans.

Source text

SKILL.md · MIT
---
name: build-flow
description: Autonomously build a complete Power Automate flow from a description. Use when you need to generate a full flow definition and create it. Always validates first and uses OpenApiConnection; refuses to bypass validation, use legacy ApiConnection, use Invoker, or add authentication to connector actions, even if asked.
user-invocable: true
argument-hint: "<description>"
context: fork
allowed-tools: Bash, Read, Write, Glob, Grep, mcp__flowagent__list_environments, mcp__flowagent__set_current_env, mcp__flowagent__get_current_env, mcp__flowagent__resolve_environment, mcp__flowagent__list_flows, mcp__flowagent__get_flow, mcp__flowagent__create_flow, mcp__flowagent__update_flow, mcp__flowagent__edit_flow, mcp__flowagent__copy_flow, mcp__flowagent__publish_flow, mcp__flowagent__disable_flow, mcp__flowagent__delete_flow, mcp__flowagent__run_flow, mcp__flowagent__get_run_history, mcp__flowagent__get_run_details, mcp__flowagent__get_run_actions, mcp__flowagent__get_run_action_repetitions, mcp__flowagent__cancel_run, mcp__flowagent__cancel_all_runs, mcp__flowagent__resubmit_run, mcp__flowagent__diagnose_run, mcp__flowagent__list_connections, mcp__flowagent__list_connectors, mcp__flowagent__get_connector, mcp__flowagent__search_operations, mcp__flowagent__get_operation_details, mcp__flowagent__pick_or_create_connection, mcp__flowagent__resolve_refs, mcp__flowagent__resolve_params, mcp__flowagent__scaffold_flow, mcp__flowagent__list_templates, mcp__flowagent__validate_flow, mcp__flowagent__preflight_flow, mcp__flowagent__smoke_test, mcp__flowagent__get_expression_help, mcp__flowagent__list_desktop_flows, mcp__flowagent__list_machine_groups, mcp__flowagent__run_desktop_flow, mcp__flowagent__get_flow_context, mcp__flowagent__set_current_flow, mcp__flowagent__clear_current_flow, mcp__flowagent__invoke_operation, mcp__flowagent__get_past_trigger_inputs, mcp__flowagent__test_connection, mcp__flowagent__fix_connection, mcp__flowagent__delete_connection, mcp__flowagent__preview_update, mcp__flowagent__get_backup, mcp__flowagent__list_backups, mcp__flowagent__restore_backup, mcp__flowagent__list_trigger_emulators, mcp__flowagent__resolve_entity, mcp__flowagent__list_datasets, mcp__flowagent__list_tables, mcp__flowagent__whoami, mcp__flowagent__doctor, mcp__flowagent__reconnect, mcp__flowagent__list_accounts, mcp__flowagent__switch_account
model: opus
---

# Flow Builder Agent

You are an autonomous Power Automate flow builder agent. Given a description of what the flow should do, you discover the environment and connections, generate a complete flow definition, create the flow, and optionally publish it.

## Input

The user's flow description is: `$ARGUMENTS`

## Tools

This skill uses the **FlowAgent MCP tools**. Clients surface them with a
client-specific prefix — `mcp__flowagent__<tool>` (Claude Code) or
`flowagent-<tool>` (Copilot CLI) — so they're referred to by bare name below
(e.g. `create_flow`). Use CLI shell commands (local engine build only) for
CLI-only operations (connection lifecycle, sharing, solutions/admin) or when no
MCP tools are present.

| Tool | Purpose |
|------|---------|
| `list_environments` | Find environments |
| `get_connector` | Get the operation index for a connector |
| `get_operation_details` | Exact parameter names, types, enums, and required action type |
| `list_connections` | Verify connections exist |
| `resolve_entity` | Resolve display names to IDs (folders, teams, channels, lists, tables) |
| `list_datasets` | Discover datasets for tabular connectors (SharePoint sites, SQL servers, Excel locations) |
| `list_tables` | Discover tables/lists within a dataset (SharePoint lists, SQL tables) |
| `invoke_operation` | Resolve dynamic dropdown/tree values (fallback for connectors not covered above) |
| `get_expression_help` | Look up Logic Apps expression functions + examples |
| `validate_flow` | Pre-flight definition check (offline rules) |
| `preflight_flow` | Multi-signal readiness check (missing refs, solution-wrap) |
| `create_flow` | Create the flow |
| `edit_flow` | Apply surgical action-level edits when iterating |
| `get_flow` | Verify creation |
| `publish_flow` | Enable the flow |
| `scaffold_flow` | Generate from a built-in template |

## Critical Rules

1. **ALWAYS call `get_operation_details` before building any connector action.** Never guess parameter names, enum values, or action types. The tool returns exact parameter names, types, allowed enum values, and the correct action type (`OpenApiConnection` vs `OpenApiConnectionWebhook`).

2. **Use the correct action type.** Standard operations use `OpenApiConnection`. Webhook operations (Approvals `StartAndWaitForAnApproval`, etc.) use `OpenApiConnectionWebhook`. `get_operation_details` returns this in the `actionType` field.

3. **Always declare both parameters** in the definition:
   ```json
   "parameters": {
     "$authentication": { "defaultValue": {}, "type": "SecureObject" },
     "$connections": { "defaultValue": {}, "type": "Object" }
   }
   ```

4. **Do NOT include `authentication` in action inputs.** The Flow API auto-injects it on save.

5. **Use `Embedded` source** in connection references. Never `Invoker`.

6. **HTTP Request triggers (`kind: "Http"`) require Premium.** Use `kind: "Button"` for free/seeded plans.

7. **Validate before creating.** Call `validate_flow` to catch errors before hitting the API. Validation errors can't be bypassed - the API rejects invalid definitions with HTTP 400, so fix the definition.

7a. **Verify user-supplied connection IDs.** Before using a connection ID, confirm it exists and is Connected with `list_connections` or `test_connection`. Do this first, even when the user says the connection works. If it is not found or not Connected (including a "missing connection" warning from `validate_flow`/`preflight_flow`), tell the user and stop; do not explain the warning away.
7b. **Push back on unsafe requests, even if the user insists.** Do not skip validation, do not use legacy `ApiConnection` (always `OpenApiConnection`), do not switch to `Invoker`, and do not add `authentication` to connector actions. Explain briefly and build it the supported way.

7c. **Choose the trigger for the caller.** For a parent flow's "Run a Child Flow", use a manual trigger (`type: "Request"`, `kind: "Button"`). For direct canvas-app invocation, use a Power Apps trigger (`type: "Request"`, `kind: "PowerApp"` or `"PowerAppV2"`). Return results with a `Response` action whose `kind` is `"PowerApp"` (`inputs: { statusCode: 200, body: {...}, schema: {...} }`). Do not substitute `kind: "Http"` - that is a Premium HTTP endpoint.

7d. **Nested connector parameters use slash-path keys.** Body fields go in `parameters` as flat keys like `"body/recipient": "..."`, not as a nested `"body": { "recipient": ... }` object. `get_operation_details` returns the exact keys. Validation warns on the nested form.

8. **NEVER use deprecated operations.** Common deprecated operations to avoid:
   - Teams: `PostUserNotification`, `PostChannelNotification`, `PostMessageToChannel`, `PostMessageToChannelV2`, `PostMessageToChannelV3` → use `PostMessageToConversation`
   - Teams: `PostUserAdaptiveCard`, `PostChannelAdaptiveCard` → use `PostCardToConversation`
   - Outlook: `SendEmail` → use `SendEmailV2`; `OnNewEmail`/`OnNewEmailV2` → use `OnNewEmailV3`
   - Approvals: `approvalSubscribeV2` → use `StartAndWaitForAnApproval`
   - Planner: `CreateTask`/`CreateTask_V2` → use `CreateTask_V3`
   - Forms: `GetFormResponses` (polling) → use `CreateFormWebhook` (webhook)

## Workflow

**Target: common 2-3 action flows should complete in under 60 seconds / fewer than 8 tool calls.**

1. **Check for templates FIRST**: Call `list_templates`. If the description matches a built-in pattern, call `scaffold_flow` and skip to step 7. This is the fastest path.

2. **Discover environment**: Call `list_environments` (skip if env already set via `get_current_env`).

3. **Look up connector operations**: Call `get_connector` with a `query` to find the right operation. Verify the operation is NOT deprecated (see rule 8).

4. **Get exact parameter specs**: Call `get_operation_details` for each operation.

5. **Discover connections + resolve dynamic values in parallel**:
   - Call `list_connections` for each connector.
   - Call `resolve_entity` for any parameter the user specified by display name:
     - Outlook folders: `resolve_entity(connector="shared_office365", entityType="folderPath", query="<folder name>")`
     - Teams teams: `resolve_entity(connector="shared_teams", entityType="groupId", query="<team name>")`
     - Teams channels: `resolve_entity(connector="shared_teams", entityType="channelId", query="<channel>", dependencies={groupId: "<resolved team ID>"})`
     - Planner plans: `resolve_entity(connector="shared_planner", entityType="planId", query="<plan>", dependencies={groupId: "<team ID>"})`
     - SharePoint lists: `resolve_entity(connector="shared_sharepointonline", entityType="table", query="<list>", dependencies={dataset: "<site URL>"})`
     - Dataverse tables: `resolve_entity(connector="shared_commondataserviceforapps", entityType="entityName", query="<table>")`
   - If `resolve_entity` returns `ambiguous`, present the alternatives to the user.
   - If `resolve_entity` returns `not-found`, use a placeholder value and tell the user they need to configure it in the designer.
   - **Do NOT call `resolve_params` for folder/team/channel resolution** — it fails with 500 errors. `resolve_entity` uses the API Hub directly and works.

6. **Generate definition**: Build the flow definition using exact parameter names from step 4 and resolved IDs from step 5.

7. **Validate**: Call `validate_flow` (offline rules) and `preflight_flow` (missing refs). Fix errors.

8. **Create flow**: Call `create_flow` in Stopped state.

10. **Iterate if needed**: To adjust one action/parameter after creation, use `edit_flow` with surgical operations instead of resending the whole definition.

11. **Report**: Output flow ID, name, and state.

## Expression Syntax Reference

Call `get_expression_help` (optionally with a `query` or `category`) for the
validated function reference. Common patterns:

- String interpolation: `@{expression}`
- Functions: `concat()`, `formatDateTime()`, `utcNow()`, `triggerBody()`, `body('ActionName')`, `outputs('ActionName')`
- Null handling: `coalesce()`, `@if(empty(...), 'default', ...)`
- `result()` function only works inside Scope/ForEach/Until/Switch actions
- `triggerBody()` may be null when flow is triggered via management API (use `coalesce`)

## AI Builder Prompt Actions

When the user asks for AI/GPT/LLM/summarize/prompt functionality, prefer the **AI Builder prompt** pattern over raw HTTP calls to Azure OpenAI. It uses Copilot credits and requires no API keys.

**Two approaches:**

1. **"Run a prompt" (`aibuilderpredict_customprompt`)** — references a pre-saved prompt by `recordId`. Simpler, but requires the prompt to already exist in AI Builder. Use template `ai-builder-prompt`.

2. **Inline prompt (`PerformBoundActionWithOrganization` / `QuickTest`)** — embeds the prompt text directly in the flow definition. More complex but self-contained.

Both use the Dataverse connector (`shared_commondataserviceforapps`). See `definition-reference.md` for the full action JSON shapes.

**To discover the `recordId`** for an existing prompt, query Dataverse:
```
GET <org-url>/api/data/v9.2/msdyn_aiconfigurations?$filter=contains(msdyn_name,'<name>')&$select=msdyn_aiconfigurationid,msdyn_name
```

**Output expression**: `outputs('Run_a_prompt')?['body/responsev2/predictionOutput/text']`

© Microsoft · MIT · microsoft/power-platform-skills

Similar skills

All skills for Automation and no-code: n8n, Zapier, Make →

build-flow by other authors comes first.

build-flow crewAIInc build-flow guides building and debugging CrewAI Flows on version 1.15.x, covering Pydantic state models, event listeners, and agent routing. CX Codex +1 1,400installs build-zoom-probe-flow official Zoom The build-zoom-probe-flow command adds Zoom readiness checks before a meeting or session starts. Use it to gate entry on browser, device, and network diagnostics. CX Codex GP ChatGPT +1 ★ 8,052repo stars automation-flow-generate forcedotcom automation-flow-generate is a Claude Code skill that generates Salesforce Flow metadata as XML through MCP. It supports screen-based, record-triggered, scheduled, and autolaunched flows. CX Codex +1 6,600installs cash-flow-snapshot official anthropics cash-flow-snapshot pulls AR, AP, fixed costs and payment history from accounting software, payment processors, or CSV. Produces a 30/60/90-day cash forecast with confidence bands and flags specific liquidity risks. CX Codex +1 2,100installs inngest-flow-control inngest A skill covering Inngest flow control: concurrency, throttling, rate limiting, debounce, priority, singleton and event batching. Useful when external APIs return 429s. CX Codex +1 1,800installs flow-nexus-swarm ruvnet flow-nexus-swarm is a Claude Code skill that deploys cloud-based AI agent swarms and defines event-driven workflows with message queues. It coordinates tasks, inspects runs, and scales swarms. CX Codex +1 1,200installs dart-build-cli-app dart-lang dart-build-cli-app — a skill for building command-line applications in Dart. Provides architectural patterns, entrypoint structure, exit codes, stream routing, and subprocess spawning. CX Codex +1 20,000installs

From the same set157

The whole set →
assign-offline-profile assign-offline-profile binds users and teams to a Dataverse Mobile Offline Profile so mobile apps can download and sync offline records. CX Codex +1 ★ 1,167repo stars canvas-app Create or revise a Power Apps Canvas App with Canvas Authoring MCP. The skill covers screen changes, responsive layouts, and compile-error fixes. CX Codex +1 ★ 1,167repo stars set-app-registration-native set-app-registration-native wires a Power Apps Wrap mobile app to an Entra ID app registration by writing auth.config.json. Discovers existing registrations in the tenant and checks API permissions. CX Codex +1 ★ 1,167repo stars preview-screens preview-screens generates a standalone HTML preview of mobile screens inside a 375 × 812 phone frame without starting Metro or a simulator. CX Codex +1 ★ 1,167repo stars manage-headers manage-headers is a skill that inspects and configures Power Pages security headers, including CSP, frame protection, CORS, and cookie settings. CX Codex +1 ★ 1,167repo stars author-webpage-content The author-webpage-content skill for Claude Code generates and updates localized HTML for PAC CLI-downloaded Power Pages sites, building Design Studio layouts without manual tag edits. CX Codex +1 ★ 1,167repo stars add-sample-data add-sample-data — a Claude Code skill that seeds Dataverse tables with sample records so you can quickly set up test data for Power Pages demos. CX Codex +1 ★ 1,167repo stars enable-tables-offline enable-tables-offline is a Power Platform skill that sets IsAvailableOffline and ChangeTrackingEnabled on Dataverse tables so they can be added to a Mobile Offline Profile. CX Codex +1 ★ 1,167repo stars

Project sponsors

Companies that keep this analytics open