n8n Limitations on Reddit: What's True, Outdated or Misunderstood
A review checking n8n limitations reddit threads keep repeating — licensing, workflow caps, enterprise gating and scaling — against n8n's own current docs.
Checked against the cited sources on .
Scope and method: checking recurring n8n community limitations against the docs
Type n8n limitations reddit into a search bar and you'll find the same handful of complaints resurfacing year after year: licensing confusion, workflow caps, missing enterprise features, scaling headaches, and claims that error handling or pagination simply don't work. Some of these were accurate once. Others were fixed months ago. A few were never quite right to begin with.
This piece checks the n8n limitations reddit threads keep repeating against n8n's own current documentation, rather than quoting specific forum posts — no actual Reddit text was available to us as source material, so we're verifying the recurring n8n community limitations themes, not auditing individual threads.
- Licensing: is n8n really open source?
- Workflow and plan caps
- Enterprise feature gating in the free Community edition
- Queue-mode scaling and high availability
- Error handling, pagination and custom data transforms
Licensing confusion: is n8n really open source?
The most common licensing complaint is that n8n 'isn't really open source.' n8n's own licensing documentation states that the free Sustainable Use License permits using or modifying the software only for internal business purposes, not unrestricted commercial resale, which is the likely source of that complaint.
That restriction is narrower than many threads suggest. n8n's License FAQ explicitly disallows hosting n8n as a service so clients build their own workflows on your instance, but it explicitly permits consulting and automation services where an agency builds workflows for a client on an operator-controlled instance. We think treating this license as a blanket open-source dealbreaker misses the point for most ops teams: it blocks reselling hosted access to n8n itself, not the kind of internal automation work or client delivery most companies actually do.
Paid proprietary licenses also exist for enterprise customers, separate from the free community license, per n8n's documentation — though exact enterprise terms live on n8n's separate pricing page rather than the licensing docs themselves.
Sources: Community license | n8n Community license | n8n Docs, License FAQ | n8n Community license | n8n Docs
Workflow limits: true before August 2025, removed since
A frequently repeated complaint is that n8n caps how many workflows you can run. That was true for a period. According to n8n's own August 2025 pricing announcement, the company removed active-workflow limits from all plans, so every plan now includes unlimited workflows, steps and users as of August 7, 2025.
The caveat worth keeping is that n8n's announcement notes the change only takes effect once a self-hosted instance is updated to the latest version — an old, unpatched self-hosted install could still behave as if the cap exists. Anyone citing this limitation from an older post should check their instance version before assuming it still applies.
Sources: New plan, no active workflow limits — n8n's new pricing explained. – n8n Blog
Community edition vs paid plans: which features are still gated
Unlike the workflow cap, the complaint that the free Community edition lacks enterprise security and governance features remains accurate today. n8n's edition-comparison docs confirm the self-hosted Community edition still excludes SSO (SAML, LDAP), and that Business and Enterprise plans unlock features Community doesn't include, such as SSO, environments and external secrets.
| Feature | Community (free) | Business/Enterprise |
|---|---|---|
| SSO (SAML, LDAP) | Not included | Included |
| Environments | Not included | Included |
| External secrets | Not included | Included |
| Full workflow version history | Last 24 hours only | Full history |
If your evaluation assumes the free edition covers single sign-on or secret management for a growing team, we'd flag that assumption now rather than after budgets are set — these are documented paid-tier gates, not oversights likely to be reversed.
Workflow history follows the same pattern but with a partial exception. n8n's docs restrict full workflow history to n8n Cloud Enterprise and self-hosted Enterprise, yet versions from the last 24 hours remain available to all users, including free-tier ones — a detail that complicates the blanket claim that community users have zero version history.
Sources: Compare editions | Deploy | n8n Docs, View change history | Build | n8n Docs
Scaling complaints: queue mode, binary data and multi-main visibility
Scaling complaints also hold up well. n8n's queue-mode documentation confirms that running n8n in queue mode does not support binary data storage in the filesystem, pushing teams toward S3-compatible external storage instead.
High-availability setups face a similar gate: n8n's docs restrict multi-main setup for queue mode to self-hosted Enterprise, with no equivalent offered on n8n Cloud. Complaints about limited high availability on lower tiers are accurate as documented.
- Queue mode: binary data storage in the filesystem is unsupported
- Multi-main (HA) setup: self-hosted Enterprise only
- n8n Cloud: no multi-main equivalent documented
Sources: Enable queue mode | Deploy | n8n Docs
Error handling, pagination and custom code: misunderstandings worth retiring
Some repeated n8n community limitations aren't limitations at all. 'n8n has no error handling' is one: n8n's error-handling docs state that an error workflow lets you control how n8n responds to a failed execution, and a dedicated Error Trigger node exists specifically to build those workflows.
'You can't paginate APIs in n8n' and 'you need external code for real data transforms' follow the same pattern. The HTTP Request node documentation confirms native pagination support, though each API's own pagination scheme still needs manual configuration. The Code node lets users write full JavaScript or Python as a workflow step, directly inside the canvas.
Our practical take is that many of these claims survive mainly because no one rechecks them against the current docs, not because they remain accurate once someone actually looks.
Sources: Expressions versus data nodes | Build | n8n Docs, Pagination | Build | n8n Docs, Handle errors gracefully | Build | n8n Docs, Error Trigger | Nodes | n8n Docs
What this means for an ops or IT evaluation
Before a recurring n8n limitations reddit complaint shapes a procurement decision, check it against current docs and the pricing page directly, since licensing and feature gating have changed more than once, including the August 2025 pricing overhaul.
None of this replaces checking your own instance. A complaint can be documented and accurate in general while not applying to your specific plan, version or setup.
