Is n8n Worth It? (And Is n8n Dead?)

Two questions come up in almost every automation conversation we have: “is n8n worth it?” and, usually half-joking, “is n8n dead?” Both are fair. n8n is everywhere at the moment, and anything hyped that hard gets a backlash. This is our take, from a team that uses n8n on real client builds.

First, what n8n actually is

n8n is a visual workflow tool. You drag nodes (each one a single step, like reading a form or adding a contact) onto a canvas and wire them together. It moves data between your apps and runs logic on a trigger or a schedule: “when a form is submitted, enrich the lead, add it to the CRM, and send a Slack message.” It’s in the same family as Zapier and Make, with two big differences. It’s far more flexible, and you can self-host it (run it on your own server) so your data stays on your own infrastructure.

Is n8n dead?

No. The community is huge, the project ships updates constantly, and it’s become one of the default ways people connect AI to the rest of their stack. The “is n8n dead” searches are mostly clickbait and the usual swing of the hype cycle. AI agents have given it more work, not less: it’s a good way to coordinate calls between models, tools and your existing apps.

Park that question. The one that matters for your business is the second one.

Is n8n worth it? Where it earns its place

For plenty of jobs, yes, and we reach for it ourselves. n8n is a good fit when you want to:

• Prototype fast. Wiring up a proof of concept on a canvas is quicker than writing it from scratch. You find out whether an idea works before paying for a real build.
• Glue standard apps together. If the job is “move data from A to B to C” with tools that already have n8n nodes, it’s hard to beat.
• Run internal, low-stakes automations. Notifications, simple syncs, weekly digests: jobs where the odd hiccup isn’t a disaster.
• Keep your data in-house. Self-hosting is a real advantage over the cloud-only tools if privacy matters.

If that’s you, n8n is worth it. This isn’t an anti-n8n piece, and we use it where it fits. The next part is the one people don’t hear enough.

Where n8n starts to hurt

The trouble is that “quick to wire up” and “solid in production” aren’t the same thing, and plenty of businesses find the gap the hard way. As the work gets more important, a few problems tend to show up:

• Debugging a big canvas is painful. A workflow that looked tidy at ten nodes is a plate of spaghetti at fifty. Finding why something failed means clicking through the graph node by node.
• Error handling and monitoring are bolt-ons. Proper retries, alerts and logs are things you have to remember to build in, and it’s easy to end up with a workflow that fails silently.
• Complex logic fights the visual model. The moment you need real branching, loops or anything custom, you’re writing code inside function nodes anyway, just with worse tooling around it.
• Costs and limits scale with volume. On the cloud plans you pay per execution (each time a workflow runs), and high-volume workflows add up. Self-hosting removes that but hands you the server upkeep instead.
• You’re building on someone else’s platform. Your logic lives inside n8n’s model. Moving off it later, or handing it to a developer, isn’t always clean.

None of this makes n8n a bad tool. It has a sweet spot, and businesses often push work past it because the tool made starting so easy.

Most of what n8n does can be built into a system you own

This is the part we care about most. Strip a typical n8n workflow back to what it actually does (receive an event, call a few APIs, run some logic, store a result, notify someone) and almost all of it is standard software. There’s nothing special in the nodes. The same job can be built directly into a proper system, and for anything that matters, that’s usually the better result.

• It fits your exact process instead of bending your process to fit the available nodes.
• Real error handling, logging and tests are built in from the start, so it fails loudly and safely instead of silently.
• No per-execution pricing and no platform ceiling. It runs on infrastructure you control and grows without a per-run meter.
• You own it outright. Every line of code is yours, documented and handed over, with no lock-in to a platform’s way of doing things. It’s the same reason we build custom CRMs instead of stacking subscriptions.

That’s how we work in general. Almost anything you can describe can be built, and the goal is a system that quietly works for you, not a tool you keep working around. For the mechanics of how automated workflows run, we go deeper in what is AI workflow automation.

n8n or a custom build?

It isn’t either/or, and we use both. A simple rule of thumb:

• Reach for n8n when you’re prototyping, connecting standard apps, or running low-stakes internal automations you’re happy to keep an eye on.
• Build it properly when the process is core to the business, runs at volume, needs to be reliable, or you want to own it outright instead of renting a platform.

The mistake isn’t using n8n. It’s letting something business-critical live on a canvas that was only meant to be a quick fix, then paying for it when it breaks at the worst moment. We wrote about that trap in how to automate a business process without breaking it.

People also ask

Is n8n dead?

No. n8n is actively developed and widely used, and AI agents have given it more to do, not less. The “is n8n dead” question is mostly hype-cycle noise. The real question is whether it’s the right tool for your specific job.

Is n8n better than Zapier or Make?

For flexibility and data control, usually yes: n8n does more and can be self-hosted. Doing more also means more to manage. For simple, standard automations, Zapier or Make can be quicker to set up. For anything business-critical, a custom build often beats all three.

Should I use n8n or build a custom system?

Use n8n for prototypes, glue and low-stakes internal jobs. Build custom when the process is core to the business, runs at volume, or needs to be reliable and owned. Most of what n8n does can be built into a system you fully control, and for the work that matters, that’s usually worth it.

Our answer, for what it’s worth. n8n is worth it when somebody will own it, and a liability when nobody will. It rewards a person who enjoys the tinkering, and quietly rots without one. Where a business doesn’t have that person, a managed tool costs more per month and less per year.