Power Automate vs. self-hosted n8n: when SMBs should pick which

Self-hosted n8n has crossed a real adoption threshold among technical SMBs in the last 18 months — and the question we now hear weekly is whether to stand up an n8n instance instead of paying Microsoft Power Automate per-flow. Both will run the same Zapier-style integrations. The trade is not features; it’s operations cost, AI-tooling reach, and the audit story.

Here is the honest comparison for a 30–300-person SMB already on Microsoft 365. No vendor loyalty — we ship both.

Self-hosted n8n is free to license and expensive to operate. Power Automate is the reverse. Pick the cost you’d rather pay.

1. The licence-vs-ops trade

n8n self-hosted

• Licence: $0 for the Community edition (Sustainable Use Licence — allows internal-business use, not as part of your commercial product). $50/month for n8n Cloud Starter if you’d rather not self-host. Enterprise tier starts at $667/month.
• Hosting: A small Azure App Service or Container App, Postgres, queue mode if you scale past ~20 concurrent executions. Realistic all-in: $80–250/month for an SMB workload.
• Operations: Someone owns Docker updates, credential rotation, queue tuning, the workflow Git repo and the backup. Budget 4–8 engineer-hours/month steady state, more during n8n version upgrades.

Power Automate

• Licence: $15/user/month for the per-user plan, or $100/month for a per-flow plan covering 5 flows. AI Builder credits sold separately ($500/month for 1M credits, or pooled in M365 Copilot at lower rates).
• Hosting: Microsoft’s problem.
• Operations: Maker support, governance (Managed Environments, DLP policies, CoE Starter Kit). Budget 2–4 hours/month after the initial setup.

2. Where n8n genuinely wins

• Open-source connectors for the long tail. n8n has 400+ integrations and lets you write custom nodes in TypeScript. If you depend on a niche vertical SaaS, the community node is often the only first-class connector that exists. Power Automate’s custom connector story works but requires Premium per-user.
• Self-host inside your VPC. If your data policy says no SaaS automation touches PHI/PII, n8n on your own infrastructure is a defensible answer in a way Power Automate isn’t.
• AI agent workflows (the LangChain story).n8n’s built-in AI Agent node + the LangChain integrations are ahead of Power Automate for chained-LLM, tool-using workflows — particularly when you want to swap models freely.
• Version control as first-class. Workflows export to JSON and live in Git. Power Automate has solutions + ALM, but n8n’s Git story is simpler.

3. Where Power Automate wins (for an M365 SMB)

• You already paid for it. M365 Business Standard and above include the seeded Power Automate plan. Most SMBs we audit are running 4–8 free flows already and don’t know it.
• Microsoft Graph + SharePoint + Dataverse reach. Triggers on Teams messages, Outlook flags, SharePoint list changes, calendar events — n8n can reach these via Graph API connectors, but Power Automate is one click and inherits the user’s permissions.
• AI Builder + Copilot Studio integration. If you’re running document processing or invoice extraction on forms volume, AI Builder is the lowest-friction path. n8n + a Document Intelligence node can match capability but you’re building the assembly.
• Governance. Managed Environments + Purview + DLP policies + audit logs in the M365 admin center. n8n has audit logs in the Enterprise tier; the Community edition does not. For a regulated SMB, this matters.
• The hands-off operations story. No one is paged at 2am because the n8n container OOMed during a queue spike.

4. The hybrid pattern we ship most often

For SMBs with one engineer on staff and a mix of M365-native and non-M365 workloads, the right answer is usually both:

1. Power Automate owns anything that triggers on Outlook / Teams / SharePoint / Dataverse, anything that writes back into M365, anything that uses AI Builder, and anything a business user maintains.
2. n8n self-hosted owns the long-tail SaaS connectors, the agent / LangChain workflows where model choice matters, and anything that has to run inside your VPC for data-policy reasons.
3. The handoff is via Power Automate calling n8n webhooks, or n8n calling Graph API directly with a service principal.

5. When to pick which (the 30-second test)

Skip n8n if:

• You don’t have an engineer who owns infrastructure already.
• Your flows are 80% M365-native triggers and actions.
• You’re in a regulated vertical and need audit logs on every execution from day one (then pay for n8n Enterprise, or use Power Automate).
• The team building flows is business-side, not IT.

Skip Power Automate if:

• You’re not on Microsoft 365 (the licence math collapses).
• You need a connector that genuinely doesn’t exist in PA but does in n8n’s community library, and building a custom connector isn’t worth it.
• You’re building agent / LangChain workflows where being able to swap models per node matters more than governance.
• You have a hard policy against any flow execution running outside your network boundary.

6. What to read next

The Power Automate vs Zapier piece is the right next read if you’re also evaluating Zapier. If you’re scoping AI agent work specifically, the Copilot Studio vs custom agents post covers the build-vs-buy framework one layer up.