Pipedream API + MCP vs Microsoft Power Automate

Pipedream API + MCP

Managed OAuth per end user across 3,000+ apps, through API, SDK or MCP. Public changelog's last entry is 1 October 2025.

Microsoft Power Automate

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.

Pipedream API + MCP

1. Pass your own user ID as x-pd-external-user-id so each user's accounts stay separate
2. Send x-pd-app-slug to load one app's tools rather than 10,000
3. Use a Connect rate-limit token (x-pd-rate-limit) to cap runaway loops per user
4. Check isError on tool results before treating a call as done
5. Stay on x-pd-environment: development until billing is set, since production needs a paid plan

Microsoft Power Automate

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/