Stacks and Flows

n8n

Open-source workflow automation with 400+ integrations and native AI agent nodes — self-host or cloud, no lock-in.

n8n freemium Updated 2026-05-09
Visit n8n →

Pros

  • Self-host for full data control; cloud version exists when you want managed
  • Code nodes (JavaScript/Python) escape hatch when no-code hits its ceiling
  • Native AI Agent + LangChain nodes ship in core, no plugin gymnastics
  • 400+ integrations and a fast-moving community on a fair-code license
  • Public, well-documented affiliate program (30% recurring × 12 months on cloud referrals)

Cons

  • License is "Sustainable Use" (fair-code), not OSI-approved open source — read the fine print before commercial redistribution
  • UI/UX still trails Make.com on polish for non-developers
  • Self-hosting is "free" in license cost only; ops, upgrades, and SSO add real bills
  • Cloud pricing per workflow execution surprises some teams at scale

Best for

  • Developers and ops teams who want a workflow tool without vendor lock-in
  • AI-heavy automations where you want to mix LLM agents and traditional integrations
  • Internal tools where data residency or self-hosting is a hard requirement

What it is

n8n is a workflow automation platform that sits in the same ring as Zapier and Make.com but plays a different game: source-available, self-hostable, and built for people who are comfortable seeing — and writing — code when needed. Workflows are visual graphs of nodes; each node is a typed integration, a control structure, or a code block. Released under the fair-code “Sustainable Use License”, it can be self-hosted free for internal use, run in n8n Cloud, or embedded by ISVs under a separate commercial license.

In 2024–2025 n8n leaned hard into AI: native AI Agent nodes, LangChain integration baked into core, vector store nodes, and tool-calling primitives. As of 2026 it ships 400+ integrations and is one of the fastest-growing automation projects on GitHub.

Who it’s for

n8n is the default recommendation for developers, indie builders, and small ops teams who want Zapier-class capability without the per-task pricing or the data-leaving-your-server problem. It’s especially strong for anyone building AI agents that need to also do boring things — query a Postgres database, post to Slack, write to S3 — because it treats LLMs as just one more node type rather than the center of the universe.

It’s a poor fit for non-technical solo operators who genuinely need zero-config and don’t have anyone to run a server. Those people belong on Zapier or Make.

Strengths

  • Self-hosting that actually works. Docker compose, n8n CLI, official Helm charts — production deployments are documented and battle-tested.
  • AI-native without being AI-only. Agent and tool-calling nodes coexist with HTTP, database, and SaaS integrations. The same workflow can call Claude, hit a Postgres, send a Telegram message, and update Airtable.
  • Code escape hatch. Function nodes accept arbitrary JS or Python. When no-code runs out, you don’t have to migrate.
  • Fair pricing on cloud. The execution-based pricing model on n8n Cloud is generally cheaper than Zapier task pricing for medium-volume workflows.
  • Real affiliate economics. 30% recurring × 12 months on cloud signups is one of the better deals in the category.

Weaknesses / Watch out

  • “Open-source” is a marketing word here. The Sustainable Use License restricts what counts as “internal business” use and forbids competing as a multi-tenant service. If you’re a consultancy reselling n8n-as-a-service, talk to a lawyer first.
  • Self-hosting drift. The free tier of self-hosting omits SSO, audit logs, and external secrets — you’ll either upgrade to the Enterprise license or end up writing duct tape.
  • UX gaps. Branching, error handling, and sub-workflow re-use are functional but visibly less polished than Make.com.
  • Lock-in vector. Workflows are JSON-portable but the node ecosystem is n8n-specific. Migration to Activepieces or Windmill means rewriting.

Best paired with

  • Anthropic Claude or OpenAI as the LLM backend behind the AI Agent node — keep the model choice swappable rather than hard-coded.
  • Supabase or Postgres for state, vector storage, and audit logs your workflows can write to.
  • Activepieces as a comparison candidate when evaluating fully OSI-licensed alternatives.

Lock-in score

Medium. Workflow JSON exports cleanly and the integrations follow predictable patterns, but every n8n-specific node (the AI Agent node, the LangChain wrappers, custom community nodes) has to be rewritten when you migrate. If lock-in worries you, the practical mitigation is: keep complex business logic in code nodes (portable) rather than chains of n8n-specific nodes (not portable), and document your workflows alongside the code that calls them.

Verdict

Recommended. n8n is the strongest single bet in the workflow category for 2026 if you value the option to self-host and care about owning your automations. It’s not the easiest entry point — Zapier wins that — but it has the best ceiling-to-floor ratio of the lot. Affiliate program is one of the cleanest in the category, which doesn’t change the editorial recommendation but does mean the incentives are aligned.

Sources

FAQ

Is n8n free?
n8n is freemium. Check the official pricing page for current tiers and limits.
What is n8n best for?
Developers and ops teams who want a workflow tool without vendor lock-in AI-heavy automations where you want to mix LLM agents and traditional integrations Internal tools where data residency or self-hosting is a hard requirement
What are the main downsides of n8n?
License is "Sustainable Use" (fair-code), not OSI-approved open source — read the fine print before commercial redistribution UI/UX still trails Make.com on polish for non-developers Self-hosting is "free" in license cost only; ops, upgrades, and SSO add real bills
Who should use n8n?
Open-source workflow automation with 400+ integrations and native AI agent nodes — self-host or cloud, no lock-in. See our review for the full pros and cons.