n8n is the best workflow tool for most teams. But it has gaps that bite you when you try to treat workflows like production code.
n8n is a visual workflow automation tool. You connect nodes on a canvas to build automations — think Zapier, but self-hosted and more powerful. I’ve used it to save companies thousands in SaaS fees.
But recently, I hit a wall. I tried to write a unit test for a lead router — verify that “high-value” leads go to the high-value sales team before deploying.
I couldn’t do it.
n8n doesn’t have built-in testing. No way to define expected results. No way to automatically check your logic. This is the gap between n8n as a prototyping tool and n8n as production infrastructure.
Most teams don’t see this hole until they fall in.
The Testing Problem
In software engineering, automated tests ensure your code works before you deploy. You change something, run the tests, and find out immediately if you broke anything.
n8n doesn’t have this.
| What Engineers Expect | What n8n Offers |
|---|---|
| Automated tests | Manual clicks |
| Test success & failure paths | Pin one sample |
| Pass/Fail report | Read the logs |
| Protection from breaking changes | Nothing |
Without native tests, you export workflows as JSON and build your own testing harness. You build tools to test the tool you bought. (We cover why this matters and how to work around it.)
This matters because workflow errors are silent. A bad code deploy crashes the app — you notice. A bad workflow deletes leads while you sleep — you might not notice for days.
The Collaboration Problem
n8n offers “Source Control” in their enterprise plan. It sounds like what engineering teams use: branches, version history, safe merging.
It isn’t.
n8n limits you to two branches. Saving forces you to save all workflows at once — you can’t save just one.
You cannot:
- Save one workflow independently
- Merge changes from different people safely
- See who changed what, when
Imagine writing a book with a friend, but saving your chapter overwrites the entire book. If your friend fixed a typo in Chapter 1 while you wrote Chapter 10, one of you loses work.
Teams end up writing backup scripts to work around this. A messy solution for a problem that shouldn’t exist.
The License Problem
n8n calls itself “fair-code.” It looks like open source, but isn’t.
Open source lets you do anything with the code. n8n’s “Sustainable Use License” has restrictions.
The big rule: You cannot sell n8n.
| Use Case | Allowed? |
|---|---|
| Automate your business | ✅ Yes |
| Personal projects | ✅ Yes |
| SaaS product using n8n | ❌ No |
| Hosting n8n for others | ❌ No |
This matters if you’re building a company on n8n. Your business model might violate their license. I’ve seen companies rebuild entire architectures because they skipped the fine print.
What This Means
n8n is still the best option for most teams. It beats Zapier on price and power. But treat it with awareness:
For small internal tools: Community Edition is perfect. Accept manual testing.
For engineering teams: Budget time to build your own safety nets. n8n won’t provide them.
For product builders: Read the license. Talk to a lawyer if you’re building something commercial.
n8n is powerful. But it’s missing the safety infrastructure that engineers expect from production systems. Know where the guardrails end. Or ask whether workflows are the right paradigm at all.
Tired of working around n8n’s limitations? OpenClaw handles email, follow-ups, and lead routing without workflow plumbing — self-healing, no nodes to debug. Compare hosting options.