# Node-RED vs Microsoft Power Automate

> Microsoft Power Automate scores 62 (B) to Node-RED's 61 (C) for workflow automation. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/node-red-vs-power-automate
- Markdown: https://www.anchorterminal.com/compare/node-red-vs-power-automate.md (~2,500 tokens)
- Slim: https://www.anchorterminal.com/compare/node-red-vs-power-automate.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/node-red-vs-power-automate.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

Microsoft Power Automate scores 62 (B) on agent readiness against Node-RED's 61 (C), and leads in 4 of 7 scored categories. Node-RED leads on reliability, payments & pricing and maintenance & community. Both do workflow automation.

- Node-RED: grade C, 61/100, rank #486 of 950. Markdown https://www.anchorterminal.com/tools/node-red.md · JSON https://www.anchorterminal.com/api/v1/tools/node-red.json
- Microsoft Power Automate: grade B, 62/100, rank #447 of 950. Markdown https://www.anchorterminal.com/tools/power-automate.md · JSON https://www.anchorterminal.com/api/v1/tools/power-automate.json
- Best workflow automation platforms with APIs for AI agents: https://www.anchorterminal.com/best/workflow-automation/index.md
- All 108 workflows comparisons: https://www.anchorterminal.com/compare/workflow-automation/index.md

## Which one, for what

### Node-RED (C)

Good for: Owners who want event-driven flows on their own machine or device, with a large library of community nodes, and an agent that deploys or edits flows as JSON.

Ahead on:
- Reliability, 90 against 63
- Payments & pricing, 60 against 25
- Maintenance & community, 81 against 76

Also in its favour:
- Open source

Watch for: No OpenAPI file, `llms.txt` or SDK. The Admin API is documented as 20 hand-written pages on nodered.org

### Microsoft Power Automate (B)

Good 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:
- Schema & documentation, 68 against 41
- Agent ergonomics, 69 against 44
- Security & auth, 61 against 51
- Transparency & trust, 76 against 65

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


## Score by category

| Category | Weight | Node-RED | Microsoft Power Automate | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 90 | 63 | Node-RED +27 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 41 | 68 | Microsoft Power Automate +27 |
| Agent ergonomics | 13% (16.2 this run) | 44 | 69 | Microsoft Power Automate +25 |
| Security & auth | 14% (17.5 this run) | 51 | 61 | Microsoft Power Automate +10 |
| Payments & pricing | 10% (12.5 this run) | 60 | 25 | Node-RED +35 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 81 | 76 | Node-RED +5 |
| Transparency & trust | 7% (8.8 this run) | 65 | 76 | Microsoft Power Automate +11 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **61 · C** | **62 · B** | |

## Facts side by side

| Fact | Node-RED | Microsoft Power Automate |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | OpenJS Foundation | Microsoft |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | Proprietary service under the Microsoft Product Terms for Microsoft Power Platform |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-08 | 2026-10-02 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | 2026-09-01 |
| Customer content may train models |  | yes |
| Terms restrict automated access |  | not found in the text |
| Terms restrict benchmarking |  | not found in the text |
| Terms or service can change without notice |  | not found in the text |
| Arbitration or class-action waiver |  | not found in the text |
| Popularity | 24k stars, 55k npm/wk | 11k PyPI/wk |

## Verdicts

**Node-RED.** Node-RED's Admin HTTP API covers flows, nodes and settings in 20 documented methods, with read and write permissions per resource and a revision check on deploys. It has no OpenAPI file, no pagination and no SDK, and a default install accepts API calls from anyone who can reach port 1880.

**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.

## Before you call either

### Node-RED

1. Call `GET /auth/login` first. An empty object means no authentication is set and every Admin API call is open
2. Send `Node-RED-API-Version: v2` and the last `rev` on `POST /flows`, and re-read the flows on a 409
3. Set `Node-RED-Deployment-Type` to `nodes` or `flows` to restart only what changed. The default `full` stops every node
4. Prefer `GET /flow/:id` and `PUT /flow/:id` for one tab. `GET /flows` returns every node in the runtime
5. Treat `flows.write` and `nodes.write` as code execution on the host. Function nodes run JavaScript and `POST /nodes` installs npm modules

### 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, Node-RED or Microsoft Power Automate?

Microsoft Power Automate scores 62 (B) on agent readiness against Node-RED's 61 (C), and leads in 4 of 7 scored categories. Node-RED leads on reliability, payments & pricing and maintenance & community.

### Do Node-RED and Microsoft Power Automate need an API key?

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

### Can an agent call Node-RED and Microsoft Power Automate without installing anything?

No hosted endpoint is listed for Node-RED. No hosted endpoint is listed for Microsoft Power Automate.

### Are Node-RED and Microsoft Power Automate open source?

Node-RED is open source (Apache-2.0). No open-source release is listed for Microsoft Power Automate.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/node-red-vs-power-automate.json, and with the fewest tokens: https://www.anchorterminal.com/compare/node-red-vs-power-automate.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "node-red", "b": "power-automate"}`. From a terminal: `anchor compare node-red power-automate`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/node-red.json and https://www.anchorterminal.com/api/v1/tools/power-automate.json

## Other comparisons with Node-RED or Microsoft Power Automate

- [Activepieces API + MCP vs Node-RED](https://www.anchorterminal.com/compare/activepieces-vs-node-red.md)
- [Activepieces API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/activepieces-vs-power-automate.md)
- [Gumloop vs Node-RED](https://www.anchorterminal.com/compare/gumloop-vs-node-red.md)
- [Gumloop vs Microsoft Power Automate](https://www.anchorterminal.com/compare/gumloop-vs-power-automate.md)
- [Kestra vs Node-RED](https://www.anchorterminal.com/compare/kestra-vs-node-red.md)
- [Kestra vs Microsoft Power Automate](https://www.anchorterminal.com/compare/kestra-vs-power-automate.md)
- [Make API + MCP vs Node-RED](https://www.anchorterminal.com/compare/make-vs-node-red.md)
- [Make API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/make-vs-power-automate.md)
- [n8n API + MCP vs Node-RED](https://www.anchorterminal.com/compare/n8n-vs-node-red.md)
- [n8n API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/n8n-vs-power-automate.md)
- [Node-RED vs Paragon ActionKit + MCP](https://www.anchorterminal.com/compare/node-red-vs-paragon.md)
- [Node-RED vs Pipedream API + MCP](https://www.anchorterminal.com/compare/node-red-vs-pipedream.md)
- [Node-RED vs Prismatic](https://www.anchorterminal.com/compare/node-red-vs-prismatic.md)
- [Node-RED vs Tray.ai API + MCP](https://www.anchorterminal.com/compare/node-red-vs-tray.md)
- [Node-RED vs Windmill API + MCP](https://www.anchorterminal.com/compare/node-red-vs-windmill.md)
- [Node-RED vs Workato API + MCP](https://www.anchorterminal.com/compare/node-red-vs-workato.md)
- [Paragon ActionKit + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/paragon-vs-power-automate.md)
- [Pipedream API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/pipedream-vs-power-automate.md)
- [Microsoft Power Automate vs Prismatic](https://www.anchorterminal.com/compare/power-automate-vs-prismatic.md)
- [Microsoft Power Automate vs Tray.ai API + MCP](https://www.anchorterminal.com/compare/power-automate-vs-tray.md)
- [Microsoft Power Automate vs Windmill API + MCP](https://www.anchorterminal.com/compare/power-automate-vs-windmill.md)
- [Microsoft Power Automate vs Workato API + MCP](https://www.anchorterminal.com/compare/power-automate-vs-workato.md)