All skills
github avatar

/flowstudio-power-automate-build

@0ccadfd official
by githubgithub/awesome-copilot40k stars
5,040

Build, scaffold, and deploy Power Automate cloud flows using the FlowStudio MCP server. Your agent constructs flow definitions, wires connections, deploys, and tests — all via MCP without opening the portal. Load this skill 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 — see https://mcp.flowstudio.app

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/flowstudio-power-automate-build

This session only. Nothing lands on disk.

referencesflow-schema.md

≈1.3k tokens on demand. Your agent reads this file only when SKILL.md points to it.

FlowStudio MCP — Flow Definition Schema

The full JSON structure expected by update_live_flow (and returned by get_live_flow).


Top-Level Shape

{
  "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "$connections": {
      "defaultValue": {},
      "type": "Object"
    }
  },
  "triggers": {
    "<TriggerName>": { ... }
  },
  "actions": {
    "<ActionName>": { ... }
  },
  "outputs": {}
}

triggers

Exactly one trigger per flow definition. The key name is arbitrary but conventional names are used (e.g. Recurrence, manual, When_a_new_email_arrives).

See trigger-types.md for all trigger templates.


actions

Dictionary of action definitions keyed by unique action name. Key names may not contain spaces — use underscores.

Each action must include:

  • type — action type identifier
  • runAfter — map of upstream action names → status conditions array
  • inputs — action-specific input configuration

See action-patterns-core.md, action-patterns-data.md, and action-patterns-connectors.md for templates.

Optional Action Properties

Beyond the required type, runAfter, and inputs, actions can include:

Property Purpose
runtimeConfiguration Pagination, concurrency, secure data, chunked transfer
operationOptions "Sequential" for Foreach, "DisableAsyncPattern" for HTTP
limit Timeout override (e.g. {"timeout": "PT2H"})
metadata Designer metadata such as operationMetadataId
Designer Metadata

For existing connector actions, preserve metadata.operationMetadataId when you edit the definition. For new connector actions or Skills/HTTP response actions, add a stable GUID and keep it stable across updates. Do not regenerate these IDs on every deploy; the designer and some run-only surfaces use them to keep action identity consistent.

runtimeConfiguration Variants

Pagination (SharePoint Get Items with large lists):

"runtimeConfiguration": {
  "paginationPolicy": {
    "minimumItemCount": 5000
  }
}

Without this, Get Items silently caps at 256 results. Set minimumItemCount to the maximum rows you expect. Required for any SharePoint list over 256 items.

Concurrency (parallel Foreach):

"runtimeConfiguration": {
  "concurrency": {
    "repetitions": 20
  }
}

Secure inputs/outputs (mask values in run history):

"runtimeConfiguration": {
  "secureData": {
    "properties": ["inputs", "outputs"]
  }
}

Use on actions that handle credentials, tokens, or PII. Masked values show as "<redacted>" in the flow run history UI and API responses.

Chunked transfer (large HTTP payloads):

"runtimeConfiguration": {
  "contentTransfer": {
    "transferMode": "Chunked"
  }
}

Enable on HTTP actions sending or receiving bodies >100 KB (e.g. parent→child flow calls with large arrays).


runAfter Rules

The first action in a branch has "runAfter": {} (empty — runs after trigger).

Subsequent actions declare their dependency:

"My_Action": {
  "runAfter": {
    "Previous_Action": ["Succeeded"]
  }
}

Multiple upstream dependencies:

"runAfter": {
  "Action_A": ["Succeeded"],
  "Action_B": ["Succeeded", "Skipped"]
}

Error-handling action (runs when upstream failed):

"Log_Error": {
  "runAfter": {
    "Risky_Action": ["Failed"]
  }
}

parameters (Flow-Level Input Parameters)

Optional. Define reusable values at the flow level:

"parameters": {
  "listName": {
    "type": "string",
    "defaultValue": "MyList"
  },
  "maxItems": {
    "type": "integer",
    "defaultValue": 100
  }
}

Reference: @parameters('listName') in expression strings.


outputs

Rarely used in cloud flows. Leave as {} unless the flow is called as a child flow and needs to return values.

For child flows that return data:

"outputs": {
  "resultData": {
    "type": "object",
    "value": "@outputs('Compose_Result')"
  }
}

Scoped Actions (Inside Scope Block)

Actions that need to be grouped for error handling or clarity:

"Scope_Main_Process": {
  "type": "Scope",
  "runAfter": {},
  "actions": {
    "Step_One": { ... },
    "Step_Two": { "runAfter": { "Step_One": ["Succeeded"] }, ... }
  }
}

Full Minimal Example

{
  "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
  "contentVersion": "1.0.0.0",
  "triggers": {
    "Recurrence": {
      "type": "Recurrence",
      "recurrence": {
        "frequency": "Week",
        "interval": 1,
        "schedule": { "weekDays": ["Monday"] },
        "startTime": "2026-01-05T09:00:00Z",
        "timeZone": "AUS Eastern Standard Time"
      }
    }
  },
  "actions": {
    "Compose_Greeting": {
      "type": "Compose",
      "runAfter": {},
      "inputs": "Good Monday!"
    }
  },
  "outputs": {}
}

Source: SKILL.md on GitHub

1 alert16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill facilitates management of Power Automate flows via an external MCP server. It performs network requests to the service provider's domain and processes environmental data, which introduces low risks related to network communication and indirect prompt injection.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: MEDIUM · 1 issue

  • Runlayer6mo

    4/7 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 0ccadfd. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 weeks ago
  • MCP
  • power-automate
  • power-automate-cloud
  • flowstudio
  • workflow-automation
  • flow-deployment
  • connector-actions
  • azure

README badge

README badge for github/awesome-copilot/flowstudio-power-automate-build

Constructs and deploys Power Automate cloud flows via the FlowStudio MCP server, handling flow definition JSON, connector wiring, and environment setup without opening the portal. Use this skill when asked to create, scaffold, or deploy Power Automate workflows programmatically, or to wire connections and build flow definitions from scratch. Requires an active FlowStudio MCP subscription and valid JWT token.

Generated from the current SKILL.md.

What is FlowStudio MCP and do I need a subscription?
FlowStudio MCP is a server that lets you build and deploy Power Automate cloud flows programmatically. Yes, a FlowStudio MCP subscription is required — see https://mcp.flowstudio.app
Can I create a flow without opening the Power Automate portal?
Yes. This skill constructs flow definitions, wires connections, deploys, and tests entirely through the MCP server, without requiring portal access.
What connectors does this skill support?
The skill supports any connector available in your environment (SharePoint, Outlook, Teams, Approvals, OneDrive, Excel, Dataverse, Forms, etc.). You call `list_live_connections` to discover which authenticated connections are available before building.
Does this skill handle both creating new flows and updating existing ones?
Yes. The `update_live_flow` tool creates a new flow when you omit the `flowName` parameter, and updates an existing flow when you provide it.
What if required connector connections don't exist in my environment?
The skill will stop and prompt you to create the missing connections in the Power Automate portal (they require browser OAuth consent), then re-run the build.

Generated from the current SKILL.md. These answers refresh after source changes.