# Microsoft Power Automate (slim)

> Microsoft's workflow builder for cloud flows across Microsoft 365, Dataverse and third-party connectors. Outside agents list, create, update and delete solution-aware flows through the Dataverse Web API, and start a flow through its HTTP request trigger.

- Full: https://www.anchorterminal.com/tools/power-automate.md (~9,600 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/tools/power-automate.json · canonical https://www.anchorterminal.com/tools/power-automate
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-08

**B · 62/100 · rank #350 of 722 · #2 in Workflow automation · not agent-ready · confidence medium**


Assessment: Cloud flows in a solution are rows an agent can read and write through the Dataverse Web API under Entra ID OAuth and security roles, with published limits and a 99.9 per cent SLA. Flows under My flows can't be managed in code, a flow's body is one hand-built JSON string, and setup needs a tenant administrator.

## Facts

- Kind: HTTP API · vendor: Microsoft · category: Workflow automation · legal entity: Microsoft Corporation · provenance 89/100
- Local only (HTTP): nuget `Microsoft.PowerPlatform.Dataverse.Client`, pypi `PowerPlatform-Dataverse-Client`
- Auth: OAuth or key · pricing: Freemium · x402: no · licence: Proprietary service under the Microsoft Product Terms for Microsoft Power Platform
- Probe metrics: not measured yet (probes haven't run)
- Management API: Dataverse Web API, OData v4, at https://<org>.api.crm.dynamics.com/api/data/v9.2/workflows. GET, POST, PATCH and DELETE on cloud flows in solutions (`category` 5). `GrantAccess`, `ModifyAccess` and `RevokeAccess` share a flow. `ExportSolution` and `ImportSolution` move flows as solution ZIP files (https://learn.microsoft.com/en-us/power-automate/manage-flows-with-code)
- Not covered: Flows under My flows that are not in a solution. The API at `api.flow.microsoft.com` is unsupported and Microsoft says breaking changes could occur. No documented run, cancel or resubmit call
- Flow definition: `clientdata`, a string of encoded JSON holding `connectionReferences` and a definition in the Azure Logic Apps workflow definition language. Required on create with `category`, `name`, `type` and `primaryentity`
- Read-only inventory API: Power Platform API version 2024-10-01 at https://api.powerplatform.com/powerautomate/environments/{environmentId}/, with `cloudFlows`, `flowRuns` and flow actions list calls added in June 2025 (https://learn.microsoft.com/en-us/rest/api/power-platform/powerautomate/cloud-flows/list-cloud-flows)
- Starting a flow: The When an HTTP request is received trigger gives each flow its own URL on a logic.azure.com host. Entra bearer token for tenant or named users, or a legacy signed URL (https://learn.microsoft.com/en-us/power-automate/oauth-authentication)
- Run history: `flowruns` rows in Dataverse for solution flows, with start and end time, status, error code and message. Kept 28 days by default, settable. Microsoft says the feed is not lossless and that `flowevents` rows signal skipped runs (https://learn.microsoft.com/en-us/power-automate/dataverse/cloud-flow-run-metadata)
- Credentials: OAuth 2.0 through Microsoft Entra ID. Delegated sign-in or an application user with a security role. A service principal can own flows but can't be a co-owner
- Rate limits: Dataverse service protection of 6,000 requests per user in a five-minute window, with `Retry-After` on 429. Flow runtime endpoints allow 4,500 invoke calls in five minutes on the Low profile and 45,000 on the others, and about 1,000 concurrent inbound calls (https://learn.microsoft.com/en-us/power-automate/limits-and-config)
- Flow limits: A run lasts at most 30 days and its history is kept 30 days. Outbound synchronous requests time out at 120 seconds. Default retry policy of 2 retries on the Low profile and 12 on Medium and High
- SLA: Service credit of 25 per cent below 99.9 per cent uptime, 50 below 99 and 100 below 95, per the SLA for Microsoft Online Services dated 1 October 2026. Downtime is counted when users' flows have no connectivity to Microsoft's internet gateway
- SDKs: Dataverse clients, not specific to flows. .NET `Microsoft.PowerPlatform.Dataverse.Client` 1.2.27 and Python `PowerPlatform-Dataverse-Client` 1.1.0 (7 October 2026). The Power Automate docs give samples for .NET and raw HTTP only
- MCP server: None for cloud flows found in the Power Automate docs. The Process Mining MCP server (nine tools) is a preview and covers process analytics, not flows (https://learn.microsoft.com/en-us/power-automate/process-mining-mcp-server-reference)
- Audit: Microsoft Purview logs flow created, edited and deleted events and permission changes once auditing is turned on, readable through the Office 365 Management API. Runs are not in Purview (https://learn.microsoft.com/en-us/power-platform/admin/activity-logging-auditing/activity-logs-power-automate)
- Free tier: Free licence with standard connectors only, a self-serve 90-day trial, 30-day admin trials, and the Power Apps Developer Plan (free Dataverse environment, 750 flow runs a month)
- Regions: A flow runs in the region of its Power Platform environment. The region table includes Europe, France, Germany, Switzerland, Norway, India, Japan and Australia (https://learn.microsoft.com/en-us/power-automate/regions-overview)
- Prices: Power Automate Premium $15 per seat per month; Power Automate Process $150 per month (plan); Power Automate Hosted Process $215 per month (plan)

- Scores: Reliability 63, Performance pending, Schema & documentation 68, Agent ergonomics 69, Security & auth 61, Payments & pricing 25, Task success pending, Maintenance & community 76, Transparency & trust 76 · total over the 7 assessed categories
- Why: Reliability, Graded on the Dataverse Web API for solution-aware cloud flows, with the HTTP request trigger noted. · Schema & documentation, Each environment serves a CSDL `$metadata` document and Learn has a reference page for the `workflow` entity type. · Agent ergonomics, `$select` and `$top` size responses, which matters because `clientdata` holds a whole flow. · Security & auth, OAuth 2.0 through Microsoft Entra ID with coarse scopes, limited by Dataverse security roles (26 of 30). · Payments & pricing, No x402, MPP or L402 (0). · Maintenance & community, Dataverse service update 9.2.26094 went to early release on 2 October 2026, and the Python Dataverse client 1.1.0 was published on 7 October… · Transparency & trust, Closed service under the Microsoft Product Terms for Microsoft Power Platform (15).
- Sources: 37, open questions: 9, both in the full twin
- Capabilities: automation.workflows, automation.apps, automation.webhooks
- JSON: https://www.anchorterminal.com/api/v1/tools/power-automate.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/power-automate.svg` or a link to https://www.anchorterminal.com/tools/power-automate from a page on microsoft.com or one of its subdomains, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

1. Filter `workflows` on `category eq 5` for cloud flows, and add `$select`, because `clientdata` holds the whole definition
2. Flows created through the API start with `statecode` 0 (off). The docs say to turn the flow on before use
3. Put the flow in a solution first. Flows that sit only under My flows are outside the supported API
4. On 429 wait the `Retry-After` seconds. Reads of `flowruns` count against the daily Power Platform request allowance
5. Treat an HTTP trigger URL with `sig=` as a secret, and prefer the tenant or named-user trigger modes with a bearer token for `https://service.flow.microsoft.com/`

## Connect

```bash
curl "https://$DATAVERSE_ORG.api.crm.dynamics.com/api/data/v9.2/workflows?\$filter=category%20eq%205%20and%20statecode%20eq%201&\$select=name,workflowid,statecode&\$top=5" \
  -H "Authorization: Bearer $DATAVERSE_ACCESS_TOKEN" \
  -H "Accept: application/json" \
  -H "OData-MaxVersion: 4.0" \
  -H "OData-Version: 4.0"
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/power-automate

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| Pipedream API + MCP | B | 65.5 | automation.workflows, automation.apps, automation.webhooks | https://www.anchorterminal.com/tools/pipedream.min.md |
| Make API + MCP | C | 58.7 | automation.workflows, automation.apps, automation.webhooks | https://www.anchorterminal.com/tools/make.min.md |
| Workato API + MCP | C | 58 | automation.workflows, automation.apps, automation.webhooks | https://www.anchorterminal.com/tools/workato.min.md |
| Activepieces API + MCP | C | 57.5 | automation.workflows, automation.apps, automation.webhooks | https://www.anchorterminal.com/tools/activepieces.min.md |
| Tray.ai API + MCP | C | 55.5 | automation.workflows, automation.apps, automation.webhooks | https://www.anchorterminal.com/tools/tray.min.md |


## Panel reviews (0, desk reviews from public material, no calls made)