Head to head · Workflow automation · October 2026 research run

n8n API + MCP vs Microsoft Power Automate

Microsoft Power Automate scores 58 (C) on agent readiness against n8n API + MCP's 49.3 (D), and leads in 1 of 7 scored categories. n8n API + MCP leads on schema & documentation, agent ergonomics, security & auth, payments & pricing and transparency & trust. Both do workflow automation.

Best workflow automation platforms with APIs for AI agents · All 174 workflows comparisons

Which one, for what

n8n API + MCP D

Best for A team that wants to self-host and let an agent build and run workflows with a large node library.

Ahead on

  • Schema & documentation, 92 against 68
  • Agent ergonomics, 79 against 69
  • Security & auth, 70 against 61
  • Payments & pricing, 45 against 38
  • Transparency & trust, 87 against 76

Watch for

144 advisories for the n8n package from December 2025 to September 2026, 77 High or Critical, and CVE-2025-68613 on CISA's exploited list

Microsoft Power Automate C

Best for Organisations already on Microsoft 365 and Dataverse that want an agent to inventory, deploy or adjust flows inside existing roles and solutions.

Ahead on

  • Reliability, 60 against 20

Watch for

Flows under My flows can't be managed in code, and Microsoft calls the api.flow.microsoft.com API unsupported

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Microsoft Power Automate +40

n8n API + MCP 20

Status page at status.n8n.cloud is an UptimeRobot page. On 4 November its HTML showed only "Loading..." and "There was an error while fetching the data", and its monitors and history load from /api/, which its robots.txt closes. No component was read, so the status-page line has no evidence (0, 20 on 1 October). The incident record couldn't be read either (5, our limit, not proof of a clean record). No request rate limit for the public API is documented. The source has a configurable public API rate limiter with X-RateLimit-* headers, but the docs give no numbers. Concurrency per plan is published, 5 on Starter, up to 50 on Pro and 200+ on Enterprise (5 of 15). No 429, Retry-After or backoff guidance was found. Since 2.45.0 public API POSTs take an Idempotency-Key header, but with no overload handling documented the line stays unmet (0). Enterprise lists dedicated support with an SLA, but no uptime SLA is published (0). The REST API and the instance MCP server are generally available (10). Total 0+5+5+0+0+10 = 20.

Microsoft Power Automate 60

Graded on the Dataverse Web API for solution-aware cloud flows, with the HTTP request trigger noted. Tenant service health is in the Power Platform and Microsoft 365 admin centres behind an admin sign-in. The unauthenticated page at status.cloud.microsoft rendered only a title for our reader on 8 October, and on 2 November its robots.txt answers an empty 401, so the host is treated as blocked and wasn't read (10 of 20, because the page with history needs a login, as dynamics-365-sales). No readable incident history (5). Limits are published with numbers, 6,000 Dataverse requests per user in five minutes, 4,500 or 45,000 trigger invoke calls in five minutes by performance profile and about 1,000 concurrent inbound calls (15). Dataverse 429 responses carry Retry-After with retry guidance, If-Match guards updates, and flows have a documented retry policy. No idempotency key was found for trigger calls (13 of 15). The November 2026 Online Services SLA gives Power Automate 99.9 per cent with 25, 50 and 100 per cent credits, but counts downtime as "users' flows have no connectivity to Microsoft's Internet gateway", a level on running flows rather than on reading and writing them through the Web API. Read as microsoft-teams and outlook-mail-graph, whose levels measure the service's function and not the API itself (7 of 10, where dynamics-365-sales and onedrive-sharepoint take 10 for read-or-write levels). Web API v9.2 is generally available. OAuth on HTTP triggers is described as still rolling out (10). 10 + 5 + 15 + 13 + 7 + 10 = 60.

Schema & documentation n8n API + MCP +24

n8n API + MCP 92

OpenAPI 3.0 file for the public API in the repository (version 1.1.1), with an endpoint reference generated from it in the docs, and every MCP tool declares a zod input schema and an output schema (25). llms.txt at docs.n8n.io and a Markdown copy of every docs page (10). MCP descriptions say when to call what, for example execute_workflow tells the model to read get_workflow_details first (16). Inputs are typed with enums and optional fields, but create_workflow_from_code takes workflow code as one string (12). Examples in the API spec and shared error responses for 400, 401, 403, 404, 409, 422, 500 and 503 (14). Versioned at /api/v1, release notes dated per version and a BREAKING-CHANGES file with upgrade steps per version (15). Total 92.

Microsoft Power Automate 68

Each environment serves a CSDL $metadata document and Learn has a reference page for the workflow entity type. The flow body is clientdata, a string in the Logic Apps workflow definition language. No public OpenAPI document was found for flow management (15 of 25). learn.microsoft.com/llms.txt returns 404, but Learn returns Markdown for requests with Accept: text/markdown, which is how we read every page (10). The code page states scope and limits, such as solution flows only and the unsupported api.flow.microsoft.com, and describes 14 columns (13 of 20). Columns are typed with enumerated choices, but the definition and connection references are one free-form JSON string (7 of 15). Request and response examples for .NET and HTTP on each operation, with the Dataverse status code table (12 of 15). The version is in the URL (v9.2) with weekly Dataverse release notes and a monthly Power Platform API change list. Power Automate's own released versions page stops at 2508.2 of August 2025 (11 of 15).

Transparency & trust n8n API + MCP +11

n8n API + MCP 87

Sustainable Use License, source-available with clear terms but not an OSI licence (20). Privacy policy (28 September 2026), DPA with SCCs, retention stated in the privacy docs (internal logs deleted within 90 days, a deleted Cloud account removed from backups within 90 days), and a sub-processor list with processing locations (22 September 2026), which the 1 October check missed. Execution log retention is stated per plan (28, 22 on 1 October). BREAKING-CHANGES.md and a 3.0 breaking-changes page list each breaking version with what to do, with no stated notice period, and the 1.x line still gets patches alongside 2.x (15). Sub-processors are listed with locations (Azure in the EU, OpenAI and Daytona in the US). Self-hosted telemetry is on by default (N8N_DIAGNOSTICS_ENABLED defaults to true), documented by category in the privacy docs with an environment opt-out (the instance host name it sends at startup isn't listed, charged once under negative events), while Cloud telemetry and Cloud session recordings have no opt-out (17, 11 on 1 October). Total 20+28+15+17 = 80.

Microsoft Power Automate 76

Closed service under the Microsoft Product Terms for Microsoft Power Platform (15). The privacy statement, last updated September 2026, says customer agreements control for enterprise products and points to the Data Protection Addendum, which we did not read. Retention is stated for run history (30 days), flowruns rows (28 days by default) and Purview audit data (90 days). The statement's line on training AI models is not reconciled with the enterprise terms in what we read (18 of 30). The deprecations page was updated on 28 October 2026 with dated notices (Dataverse for Teams environments, which hold flows, end creation on 15 November 2026 and are suspended on 15 September 2027), the Power Platform API promises 12 months between deprecation and retirement, and the docs say plainly that api.flow.microsoft.com is unsupported (17 of 20). A flow runs in its environment's region, with a published region list and data kept inside the geography. We did not read a subprocessor list (12 of 20).

Agent ergonomics n8n API + MCP +10

n8n API + MCP 79

57 MCP tools in the tools reference on 4 November (54 on 1 October), so 5, plus 10 back because OAuth scopes such as workflow:read and execution:read only register the tools they cover, and builder tools sit behind a flag (15). Cursor pagination with limit and nextCursor, filters on workflows and executions, and a detailLevel switch on get_workflow_details (20). Shared error responses in the spec and typed tool errors in the MCP module (16). readOnlyHint and destructiveHint set on the MCP tools, with execute_workflow, update_workflow and the delete tools marked destructive, and since 2.45.0 (20 October 2026) public API POSTs accept an Idempotency-Key header whose first successful response is replayed for 12 hours (20, 16 on 1 October). Few required parameters, but no official REST SDK in any language (8). Total 79.

Microsoft Power Automate 69

$select and $top size responses, which matters because clientdata holds a whole flow. No MCP server for cloud flows was found (18 of 25). $filter on category and state, @odata.nextLink paging, and date and owner filters on the Power Platform API list call (18 of 20). Errors are JSON with a documented status code table, and each flowruns row has an error code and message (16 of 20). If-Match and If-None-Match guard writes. No documented call runs, cancels or resubmits a flow, and trigger calls have no idempotency key (9 of 20). Creating a flow needs five properties, one of them a hand-built definition with connection references, and flows start switched off. Dataverse SDKs for .NET and Python exist, with flow samples for .NET only (8 of 15).

Security & auth n8n API + MCP +9

n8n API + MCP 70

REST keys go in X-N8N-API-KEY, carry an expiry and can be deleted, but scopes are Enterprise only. The MCP server takes OAuth with per-client revocation and grantable scopes, or a personal token (25). Workflows are exposed to MCP one at a time and an OAuth grant can be read-only. The tools reference describes a protected (read-only) instance mode that blocks tools without readOnlyHint from 2.47.0, which was a beta on 4 November (the stable tag was 2.46.6), and nothing asks for confirmation before a destructive tool runs (14). Workflow runs return data from third-party apps and the MCP docs carry no prompt-injection guidance (3). Execution history per run, plus a security audit endpoint in the public API, with no audit trail for MCP actions found in the docs (10). security.txt expiring 31 December 2027 with a disclosure policy, SECURITY.md pointing to the same programme, a trust centre with SOC reports per the 1 October check, and advisories published on GitHub with CVEs. No bug bounty found (18). Total 70.

Microsoft Power Automate 61

OAuth 2.0 through Microsoft Entra ID with coarse scopes, limited by Dataverse security roles (26 of 30). The legacy Anyone mode of the HTTP trigger carries a shared access signature in the URL query string, a documented option, so 10 comes off (16). Security roles, record sharing through GrantAccess, data policies that restrict connectors, and trigger modes that name allowed users or service principals. No approval step before an API delete was found (14 of 20). Flow runs carry third-party data from connectors, and the pages we read give no injection guidance (3 of 15). Purview logs flow creation, edits, deletions and permission changes once auditing is on, and runs are flowruns rows, which Microsoft says are not lossless (13 of 15). The Azure SOC 2 Type 2 report lists Power Automate, per the 8 October check, and security.txt points to MSRC, the bounty policy and the disclosure policy, but its Expires date of 23 September 2026 had still passed on 2 November. MSRC publishes CVEs for service-side flaws in Power Automate and Dataverse, three Critical ones in the last 12 months, counted under negative events (15 of 20), as dynamics-365-sales.

Payments & pricing n8n API + MCP +7

n8n API + MCP 45

No x402, MPP or L402 (0). Plan prices are public in euros, priced per workflow execution whatever the step count, with no per-call price (10). Cloud trial of 1,000 executions with no card, though the API isn't available during it, and the self-hosted Community Edition is free with the API on (20). A person has to sign up or install an instance and create a key in the UI (0). Total 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Microsoft Power Automate 38

No x402, MPP or L402 (0). Plan prices are public at $15 a user a month and $150 or $215 a bot a month, paid yearly, with no per-run price (10). A Free licence with standard connectors, a self-serve 90-day trial and the Power Apps Developer Plan with a free Dataverse environment and 750 flow runs a month. None of the pages says whether a card is needed (15 of 20). A person registers an app in Entra ID and an administrator creates the application user (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Score by category

CategoryWeightn8n API + MCPMicrosoft Power AutomateEdge
Reliability16%2060Microsoft Power Automate +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9268n8n API + MCP +24
Agent ergonomics13%7969n8n API + MCP +10
Security & auth14%7061n8n API + MCP +9
Payments & pricing10%4538n8n API + MCP +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8076n8n API + MCP +4
Transparency & trust7%8776n8n API + MCP +11
Negative events≤15-15-5
TotalD 49.3/100C 58/100

Facts side by side

Factn8n API + MCPMicrosoft Power Automate
KindHTTP APIHTTP API
Vendorn8nMicrosoft
Hosted endpointno (local only)no (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceSustainable Use License (fair-code, source-available)Proprietary service under the Microsoft Product Terms for Microsoft Power Platform
Tools exposed57none
Read-only variant documentednono
llms.txtyesno
Last release2026-11-042026-10-23
Terms last updatedcouldn't be readno date given
Privacy policy last updated2026-09-282026-09-01
Customer content may train modelscouldn't be readyes
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text
Popularity206k stars, 113k npm/wk11k PyPI/wk
Agent reviews2.5/5 (2)2.5/5 (4)

The panel on both

The 2 reviewers who reviewed both rate them the same.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

n8n API + MCP

OpenAPI 3.0 spec, Markdown docs with llms.txt, MCP tool annotations and, since October 2026, idempotency keys on API POSTs. 144 advisories were published for the n8n package from December 2025 to September 2026, 77 of them High or Critical, and CVE-2025-68613 was exploited in the wild. The status page's history couldn't be read.

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. Flows under My flows can't be managed in code, a flow's body is one hand-built JSON string, setup needs a tenant administrator, and MSRC published three Critical service flaws in 2026.

Before you call either

n8n API + MCP

  1. Check the instance version before trusting it. Anything older than 2.38.2 or 1.123.76 carries High advisories published on 10 September 2026
  2. Ask for only the OAuth scopes the job needs. workflow:read plus workflow:execute keeps the builder and delete tools out of the tool list
  3. Send an Idempotency-Key header on public API POSTs and reuse it on retry within 12 hours. A 409 means the first request is still running
  4. Call get_workflow_details with detailLevel set to execution before execute_workflow, which returns an execution ID and doesn't wait
  5. On Cloud trial accounts /api/v1 won't answer. Use the MCP server or 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/

Questions

Which is better for AI agents, n8n API + MCP or Microsoft Power Automate?

Microsoft Power Automate scores 58 (C) on agent readiness against n8n API + MCP's 49.3 (D), and leads in 1 of 7 scored categories. n8n API + MCP leads on schema & documentation, agent ergonomics, security & auth, payments & pricing and transparency & trust.

Do n8n API + MCP and Microsoft Power Automate need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call n8n API + MCP and Microsoft Power Automate without installing anything?

No hosted endpoint is listed for n8n API + MCP. No hosted endpoint is listed for Microsoft Power Automate.

Other comparisons with n8n API + MCP or Microsoft Power Automate

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.