n8n

n8n is a workflow automation tool you can run on your own server, built for people who are comfortable getting slightly technical. You connect nodes on a canvas to move data between apps, and when the visual nodes run out of road you drop in a block of JavaScript or Python and carry on. It occupies the space between no-code connectors like Zapier and writing integration scripts yourself, and it has become a common choice for building AI agents and assistants because it handles the plumbing around a model rather than just the model call.

What you can actually do with it

Anything that involves taking data from one place, reshaping it, deciding something about it and sending it somewhere else is fair game.

• Connect hundreds of apps out of the box. There are pre-built nodes for the usual suspects — CRMs, spreadsheets, databases, messaging, email, storage — plus a generic HTTP node that talks to any API with a documented endpoint.
• Write code where visual building gets awkward. Custom JavaScript or Python steps sit inside the same workflow, which avoids the usual no-code wall when a transformation gets fiddly.
• Build AI agents with guardrails. Nodes for language models, vector stores and retrieval let you assemble RAG pipelines and multi-step agents, with human-in-the-loop approval steps before anything consequential happens.
• Host it yourself. The source is public and the container runs on your own infrastructure, which matters if your data cannot leave your network for regulatory or contractual reasons.
• Handle real branching logic. Conditionals, loops, merges, error branches and retries let you build workflows that survive contact with messy data instead of failing silently.
• Debug what actually happened. Execution history shows the data passing through each node run by run, which turns “the automation broke” into a fixable problem in minutes.
• Start from community work. A large library of shared workflow templates and community-built nodes means many common jobs are already half-solved.

Who it fits best

n8n suits technically minded operators: a developer, a data-savvy ops person, an agency building automations for clients, or a small startup team that would otherwise maintain a pile of cron jobs and scripts. If someone on your team can read JSON without flinching, you will get a lot from it.

It is also the obvious candidate when self-hosting is a requirement rather than a preference — healthcare, finance, legal or European organizations with strict data residency rules.

It is a poor fit for a non-technical owner who wants to link two apps in ten minutes and never think about it again.

Things worth knowing before you commit

• It is fair-code, not open source. The Sustainable Use License permits internal use and modification but restricts reselling n8n itself as a hosted service. Read the licence before you build a product on top of it.
• Free self-hosting is not free. You pay in servers, upgrades, backups, monitoring and security patching. For a small team, cloud hosting is often cheaper once you price your own time honestly.
• Cloud billing counts executions, not steps. This is usually favourable for long workflows compared with per-task pricing elsewhere, but a workflow triggered very frequently can burn through an allowance fast. Model your expected volume.
• Some features are reserved for paid tiers. Things like single sign-on, environments and advanced logging sit in the enterprise offering rather than the community edition.
• The learning curve is real. Expressions, data structure between nodes and error handling take time to understand, and the community nodes you may come to rely on are maintained by volunteers.

Alternatives to compare it against

If you want the least friction and the widest app catalogue and do not mind per-task pricing, Zapier remains the safest default. Make (formerly Integromat) sits closer to n8n in visual power at a lower technical bar. If you are already inside the Microsoft stack, Power Automate may be included in licences you hold. And if your automations are genuinely simple, a couple of scripts or your existing tools’ native integrations may beat adding another platform.

Plan limits, execution allowances and pricing change regularly — check n8n’s own pricing page before you commit.

Further reading

• How to Recreate Any SaaS SEO Content System with n8n — a worked build in n8n itself, showing how far the node-plus-code approach goes.
• Business Process Automation Platform Essentials — the evaluation criteria to apply before choosing n8n over Zapier or Make.
• How to Automate ETL Workloads with Job Scheduling — relevant to the data-moving pipelines n8n is often self-hosted to run.
• Automate Your Business Processes: A Beginner’s Guide — how to pick which processes are worth automating before you start building nodes.

Have you used n8n?

One sentence is enough. Would you pick it again, and why or why not? We publish the critical reviews too — that is the point.