n8n Signals
What leaders and teams rolling out n8n report, with every finding tied to its evidence.
Read the findingsWhat the evidence says
Practitioner sentiment, leaders and teams
0 Mixed from 27 sources that take a side
How this figure is madeMixed overall signal, net 0 points
From 27 authors in 22 discussions. Small sample. Run a pilot on one live workflow to measure failed runs and the time spent fixing them.
- Analyzed
- 97 total sources
- Top praise
- Self-hosting & data control (5 of 5 sources) See praise evidence
- Top concern
- Failed & silent runs (7 of 7 sources) See concern evidence
Jan 2025 to Oct 2026.
79 sources from practitioners, by month and sentiment.
Team accounts lean positive. The concerns they share are license terms and runs that fail or stop without an alert, including a queue-mode instance whose memory climbs until it restarts. One former customer's company paid US$13,000 for 50 Enterprise workflows, and the next quote was far higher. Four of the 6 team sources that discuss AI agents are critical.
Positive, mixed and negative sources
The score counts each source once, as the split does. See How the numbers work.
See the evidenceBelow: 2 praise themes, 3 concerns and 1 point of agreement.
Findings
Counted for Leaders and teams rolling it out, from 30 sources. Change group
What practitioners praise
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
Self-hosting & data controlAll 5 sources on it praise itRunning n8n on the user's own infrastructure: data control, setup, and freedom from usage limits.
Counted for Leaders and teams rolling it out.
Positive
resiros, Hacker News commenter
Comment on: NetBird Is Embracing the AGPLv3 LicenseHacker News comment
The team self-hosts n8n and loves it, license and all, because it serves their work.
Positive
Gentleman9914, n8n Community member
Installing Custom Nodes from a Private NPM Registry in n8n Using pnpm Inside a Custom Docker ImageCommunity forum post
The company runs licensed, self-hosted n8n with Docker Compose, contributes PRs upstream, and builds a custom image to version its private nodes.
Positive
Alex Puzanov, Founder and Architect, ApexSmartCorp (X profile)
Automate subtitle gaps with n8nX post
A scheduled n8n pipeline lists videos without subtitle files, fetches them from a provider's API, and reports to Telegram; Puzanov estimates that it saves the media team up to 85% of that work.
Mixed
Malte Buttjer, Builder running a team's e-commerce automations in n8n
Free your Code nodesPersonal blog post, buttjer.net
Buttjer likes n8n for the boring half of the work, but says Code node source stored as a JSON string is unreviewable, so Buttjer moved it into git behind an MCP guard.
Mixed
Pragadeesh Waran, Engineer evaluating n8n for an organization
Feedback on Self-Hosting and Using n8nCommunity forum post
A Jira ticket workflow took far less time than the estimated 4 to 5 hours by API. Handling a binary upload to S3 took about six hours, with thin docs and a data flow that was hard to follow.
AI agent workflows2 of 6 sources on it praise itHow the AI Agent, LangChain, MCP nodes, and chat triggers perform when building agents and AI steps.
Counted for Leaders and teams rolling it out.
Positive, 2
Positive
Matthias Laug, CTO and co-founder of Just Eat Takeaway and TIER Mobility
n8n + Pinecone Assistant with Matthias LaugCTO podcast, YouTube
Technology leader Matthias Laug discusses building a retrieval workflow with n8n and Pinecone, and weighs automations and modern language-model workflows from a CTO perspective.
"…n8n + Pinecone Assistant with Matthias Laug CTO of Just Eat Takeaway and TIER Mobility…"
Excerpt, Matthias Laug Mixed
Malte Buttjer, Builder running a team's e-commerce automations in n8n
Free your Code nodesPersonal blog post, buttjer.net
Buttjer likes n8n for the boring half of the work, but says Code node source stored as a JSON string is unreviewable, so Buttjer moved it into git behind an MCP guard.
Mixed or negative, 4
Mixed
u/Exact-Muscle6821, Runs a small automation agency
Most "AI agent" workflows are just glorified if-else chains with extra stepsReddit post
Uses n8n's AI features constantly for bounded tasks such as PDF extraction and ticket routing, but says most published agent workflows are showpieces that break in production.
Mixed
CJavierSaldana, Self-hosted n8n user calling an MCP server on Cloudflare Workers
[MCP Client] Transport selection dropdown ignored - causes 95M failed requests retry stormGitHub issue
The MCP Client node used SSE although HTTP Streamable was selected, creating a retry loop of about 47 requests per second and 95+ million failed requests over 8 days.
Negative
sergiotapia, Hacker News commenter
Comment on: RIP Low-Code 2014-2025Hacker News comment
At work they tried Retool and n8n for months but found building internal tools with Claude Code faster and better, and the no-code AI features often failed.
Mixed
jasongill, Hacker News commenter
Comment on: N8n - Flexible AI workflow automation for technical teamsHacker News comment
Good but not great in their organization: a cheaper Zapier substitute non-technical users praise, but custom apps must be injected into the Docker container and AI features are thin.
What concerns them
Every concern practitioners raise, most raised first.
Failed & silent runsAll 7 sources on it raise it as a concernBugs, regressions after updates, stuck or dropped executions, and failures that alerted nobody.
Counted for Leaders and teams rolling it out.
Negative
brunoarueira, Hacker News commenter, former employee
Comment on: I am retiring from fulltime writing (& pseudonymity) to launch Guardian AngelHacker News comment
At a former workplace, n8n flows built by non-engineers started breaking after the last non-technical owner left, so dependent staff had to ask engineering to fix them.
Mixed
luka-mimi, Enterprise-license customer running n8n on Google Cloud Kubernetes
Webhook upgrades to versions 2.16.0 and 2.17.0 have serious bugs and require urgent attention.GitHub issue
After upgrading to 2.16.0 and 2.17.0, webhooks with a Wait node could become unresponsive; the paying enterprise customer reported no reply from support by email.
Mixed
CJavierSaldana, Self-hosted n8n user calling an MCP server on Cloudflare Workers
[MCP Client] Transport selection dropdown ignored - causes 95M failed requests retry stormGitHub issue
The MCP Client node used SSE although HTTP Streamable was selected, creating a retry loop of about 47 requests per second and 95+ million failed requests over 8 days.
Mixed
photon_garden, Hacker News commenter
Comment on: N8n - Flexible AI workflow automation for technical teamsHacker News comment
Ran n8n in production for months at their startup: good execution observability and integrations, but flaky parallelism, poor version control and pricey hosting; migrating to backend code.
Negative
fabriciomoreirao, GitHub user reporting for a team running n8n in production
High RAM usage, until it crashesGitHub issue on n8n-io/n8n
Memory on a queue-mode deployment climbs through the day to 98 to 100%, forcing restarts after an upgrade to a 32 GB EC2 instance. The reporter says moving to Docker did not stop it.
No opinion stated
Alexander Menk, iMi digital GmbH (GitHub profile)
Still need to Publish after Git Pull (Business Version)GitHub issue on n8n-io/n8n
After the team upgraded from 1.x to 2.3.5, workflows pulled from Git into its locked production instance were never published. Production kept running the old version until each workflow was republished by hand.
Mixed
neoecos, Co-founder (Hacker News commenter)
Comment on: N8n - Flexible AI workflow automation for technical teamsHacker News comment
Their company runs billing, financial reconciliation and support automations in n8n across ops, finance and product, self-hosted on Kubernetes, but it needs care and breaking changes hurt.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.An error workflow runs only when it is set in each workflow's settings. It starts with the Error Trigger and can alert by email or Slack. A run that completes with wrong data does not trigger it unless the Stop And Error node fails the run on purpose. Handle errors gracefully
Open them in the recordLicense & paid tiers6 of 7 sources on it raise it as a concernThe Sustainable Use License's limits and the features, such as SSO, sharing, and Git, that need a paid license or plan.
Counted for Leaders and teams rolling it out.
Raised as a concern, 6
Negative
seer, Hacker News commenter
Comment on: N8n raises US$180MHacker News comment
Trialled n8n as their whole backend; even self-hosted they burned through licensed executions quickly, so they coded alternatives and dropped n8n.
Negative
JimDabell, Hacker News commenter
Comment on: N8n vs. node-redHacker News comment
Wanted to embed n8n as a small part of their product for customers; n8n told them the free license forbids it and quoted a US$50k commercial license.
Negative
kaht, n8n Community member evaluating Enterprise
N8n Enterprise On-Prem License Limits (?)Community forum post
Evaluating self-hosted Enterprise, questions why the license caps active workflows and yearly executions when the customer's own servers supply all the compute.
Negative
Tadpole9181, Hacker News commenter
Comment on: N8n - Flexible AI workflow automation for technical teamsHacker News comment
Wanted shared workspaces for a small team while self-hosting, but that requires the Enterprise tier at many times the cost, making n8n unusable for them.
Negative
John Walsh, Former Enterprise customer
Feedback: self-hosted pricingCommunity forum post
Walsh's last company paid US$13,000 for an Enterprise license with 50 workflows; a new quote came in at what Walsh calls IBM or Oracle levels.
Mixed
Husne Ozmen, SRE at Fairwinds
How We Deployed, Maintained, and Migrated Production n8n on EKSCompany engineering blog post, Fairwinds
Fairwinds ran n8n on EKS under real traffic for about a year on a community Helm chart, then cut over to the official chart when local patches became hard to justify. Ozmen reports that n8n is easy to try and harder to run in production, and multi-replica main pods need an Enterprise license.
"We deployed n8n on Amazon EKS, ran it under real traffic, and later moved from a community Helm chart…"
Excerpt, Husne Ozmen
Discussed without concern, 1
Mixed
jasongill, Hacker News commenter
Comment on: N8n - Flexible AI workflow automation for technical teamsHacker News comment
Good but not great in their organization: a cheaper Zapier substitute non-technical users praise, but custom apps must be injected into the Docker container and AI features are thin.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.The Community edition leaves out SSO, projects, sharing, environments, external secrets, log streaming, and Git version control. The license limits it to internal business, non-commercial, or personal use. Compare editions
Open them in the recordMaintainability at scale4 of 5 sources on it raise it as a concernLarge workflows that are hard to read, test, review, version, or hand over.
Counted for Leaders and teams rolling it out.
Raised as a concern, 4
Negative
brunoarueira, Hacker News commenter, former employee
Comment on: I am retiring from fulltime writing (& pseudonymity) to launch Guardian AngelHacker News comment
At a former workplace, n8n flows built by non-engineers started breaking after the last non-technical owner left, so dependent staff had to ask engineering to fix them.
Mixed
Malte Buttjer, Builder running a team's e-commerce automations in n8n
Free your Code nodesPersonal blog post, buttjer.net
Buttjer likes n8n for the boring half of the work, but says Code node source stored as a JSON string is unreviewable, so Buttjer moved it into git behind an MCP guard.
No opinion stated
Alexander Menk, iMi digital GmbH (GitHub profile)
Still need to Publish after Git Pull (Business Version)GitHub issue on n8n-io/n8n
After the team upgraded from 1.x to 2.3.5, workflows pulled from Git into its locked production instance were never published. Production kept running the old version until each workflow was republished by hand.
Mixed
photon_garden, Hacker News commenter
Comment on: N8n - Flexible AI workflow automation for technical teamsHacker News comment
Ran n8n in production for months at their startup: good execution observability and integrations, but flaky parallelism, poor version control and pricey hosting; migrating to backend code.
Discussed without concern, 1
Mixed
leo_researchly, Hacker News commenter
Comment on: AI won't replace content creators (at least for now)Hacker News comment
Spent 16 full hours building a basic n8n workflow that checks blog SEO issues; it is complex, only gives recommendations, and scratches the surface.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Git-based source control and environments are available on the Business and Enterprise plans. The Community edition and Cloud Starter and Pro rely on workflow history instead. Use source control and environments
Open them in the record
Where the evidence agrees
Statements this group's sources agree on, then the ones close to agreement.
- Recurring point
Teams use n8n for internal automation and prototypes that would take longer to build and run as code.
6 supporting sources
Where it disagrees
Questions the sources split on, with the count on each side.
For leaders and teams rolling it out, no question reaches 5 sources from 3 authors, with 2 on each side.
The evidence
Whose experience this is
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on Leaders and teams rolling it out.
Leaders and teams rolling it out
30 sources. These accounts weigh license cost, failed runs, and AI agents as small teams and companies running n8n report them.
Individual users
49 sources. These accounts weigh self-hosting, running cost, and daily reliability for people running n8n for their own work.
All users
79 sources. This combined group mixes home labs and company teams that reach different conclusions.
79 sources from practitioners, by the context they work in. Filled rows count for this group.
- Individual userOne person using it for their own work49 sources
Emphasizes Self-hosting, cost, and whether work belongs in code
- Small team2 to 10 people sharing it15 sources, counted here
Emphasizes License terms, moves to code, and AI agents that fall short
- DepartmentA department, or a named company's team10 sources, counted here
Emphasizes Fast internal tools, upgrade regressions, and license cost
- IT & leadershipIT and business leaders deciding the rollout4 sources, counted here
Emphasizes Production workflows founders run, and what they take to maintain
- Organization-wideCompany-wide rollout1 sources, counted here
Emphasizes Stepstone's 3,000-employee Enterprise move and Mercedes-Benz's global platform, shown as Operator Insights; ask n8n for a reference customer at your size
What changes with scale. Individual users focus on self-hosting and running cost. Small teams criticize license terms and moves to code. Company teams report fast internal tools alongside upgrade regressions and license quotes. Two founders run billing reconciliation and a media team's subtitle pipeline in n8n, and one describes the upkeep it needs.
Where the sources come from
Where this group's sources were published.
Counted for Leaders and teams rolling it out, from 30 sources. Change group
48 sources for this group, 18 of them documentation
- Practitioner communities25, 52% of 48 sources
- Product documentation18, 38% of 48 sources
- Videos & talks3, 6% of 48 sources
- Business & engineering blogs2, 4% of 48 sources
Older evidence stays when it still applies. Records based on changed limits, prices, or bugs stay in the history with a Needs a recheck mark.
See sources by originThe record
Who each source is, how it knows, whether it still applies and what it counts toward.
Newest first, on its own page. Every count above opens its sources there.
Read all 97 sourcesAbout this read
What changed, and how we count
What changed
- The first build removed 40 sources: 29 non-English pages and 11 pages published before 2025. It added 5 team accounts from Hacker News and the n8n Community.
- A finding shows only when at least 5 sources from 3 authors discuss it. A disagreement needs at least 2 sources on each side.
- License reports now sit under License & Paid Tiers because most concern features that require a paid key. Security remains outside the themes.
- The review dropped statements on Code nodes as an escape hatch and on moving from Zapier or Make, each with 4 sources. It also dropped self-hosting versus Cloud, with only 1 source on the Cloud side.
- Oct 25, 2026: added Feature Gaps from what existing accounts state: 7 report a missing connector or node, or a limit they had to work around.
- Oct 25, 2026: adds 8 X, GitHub, newsletter, company blog, personal blog, and independent test sources.
Method
A running review of what people using n8n at work report, from individual users to company-wide rollouts. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Who counts
- Leaders and teams rolling it out
- Small team, Department, IT & leadership, Organization-wide
- Individual users
- Individual user
- All users
- Everyone in the leaders and teams and individual users groups
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
How the numbers work
- Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among IT and business leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
- Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, leaders and teams read +10 mixed (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
- Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Weighted, it read +10 Mixed; with one vote per author it reads 0 Mixed. No evidence changed.
- Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
- Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
- Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
- Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
- Disagreements. The count on each side. GILD names no winner and gives no share of all users.
- Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.
Labels on a source
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
- Documented
- Stated in official documentation.
- Reported
- A practitioner's account of their own use.
- Measured
- Backed by the source's own measurements, such as a comparative test or tracked team metrics.
- GILD analysis
- GILD's check of a claim against official documentation.
- Current
- Describes the product as it is now.
- Still applicable
- Older, and the behavior or lesson still holds.
- Needs a recheck
- May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
- Out of date
- No longer accurate. Kept in the record; counts toward nothing current.
Flagged for a recheck, of the sources that take a side: leaders and teams 3 of 27, individual users 5 of 46, all users 8 of 73.
Limits
- GILD collected public n8n accounts published in 2025 or 2026 through Hacker News's search API and the n8n Community forum. Other sources came from Reddit, GitHub issues, dev.to, X posts, a newsletter, company and personal blogs, an independent 30-day test, and four videos and podcast episodes. These counts describe the reviewed sources. They do not represent all customers. Technical builders and self-hosters dominate n8n's public accounts, so Cloud plan details come from n8n's documentation. Of the 79 sources, 30 speak for a team or company, and most raise license costs or failed runs. n8n's product page shows the dated Vodafone UK, Stepstone, and Mercedes-Benz accounts as Operator Insights, counted separately. GILD keeps an exact copy of every page, and Medium blocks that, so GILD took each author's own blog, Substack, GitHub, or X account instead.
- Sources name edition, hosting, and version inconsistently. Each record keeps the source's wording. Records about changed limits, prices, or bugs carry a Needs a recheck mark.
Every count, and the sources behind it
17 findings for 3 groups
Each row opens its sources for the group you are reading.
| Finding | Leaders and teams rolling it out | Individual users | All users | Sources |
|---|---|---|---|---|
| Current readCurrent sentiment | 8 positive, 11 mixed, 8 negative | 20 positive, 13 mixed, 13 negative | 28 positive, 24 mixed, 21 negative | Sources |
| PraiseAI agent workflows | 2 of 6 positive | 12 of 15 positive | 14 of 21 positive | Sources |
| PraiseCode & flexibility | 3 of 4 positive (under the minimum) | 6 of 12 positive | 9 of 16 positive | Sources |
| PraiseCost at volume | 2 of 4 positive (under the minimum) | 10 of 11 positive | 12 of 15 positive | Sources |
| PraiseSelf-hosting & data control | 5 of 5 positive | 7 of 9 positive | 12 of 14 positive | Sources |
| PraiseVisual building & debugging | 3 of 3 positive (under the minimum) | 3 of 4 positive (under the minimum) | 6 of 7 positive | Sources |
| ConcernFailed & silent runs | 7 of 7 raise it | 6 of 8 raise it | 13 of 15 raise it | Sources |
| ConcernMaintainability at scale | 4 of 5 raise it | 6 of 7 raise it | 10 of 12 raise it | Sources |
| ConcernSelf-hosting upkeep | 4 of 4 raise it (under the minimum) | 6 of 10 raise it | 10 of 14 raise it | Sources |
| ConcernLearning curve | 2 of 2 raise it (under the minimum) | 4 of 6 raise it | 6 of 8 raise it | Sources |
| ConcernFeature Gaps | 1 of 1 raise it (under the minimum) | 6 of 6 raise it | 7 of 7 raise it | Sources |
| ConcernLicense & paid tiers | 6 of 7 raise it | 6 of 6 raise it | 12 of 13 raise it | Sources |
| ConsensusFast internal automations | 6 supporting | 11 supporting | 17 supporting | Sources |
| ConsensusAI in bounded steps | 1 supporting (under the minimum) | 5 supporting (below threshold) | 6 supporting (below threshold) | Sources |
| ConsensusOutgrown into code | 3 supporting (under the minimum) | 7 supporting (below threshold) | 10 supporting (below threshold) | Sources |
| DisagreementShould a growing automation stay in n8n or move to code? | Keep it in n8n 1, Move it to code 3 (under the minimum) | Keep it in n8n 6, Move it to code 7 | Keep it in n8n 7, Move it to code 10 | Sources |
| Current readEvidence mix | 48 sources | 67 sources | 97 sources | Sources |
Fact checks
GILD's checks of claims against official documentation, kept apart from the source counts.
- Failed & silent runs. An error workflow runs only when it is set in each workflow's settings. It starts with the Error Trigger and can alert by email or Slack. A run that completes with wrong data does not trigger it unless the Stop And Error node fails the run on purpose. Handle errors gracefully, checked Oct 12, 2026
- Maintainability at scale. Git-based source control and environments are available on the Business and Enterprise plans. The Community edition and Cloud Starter and Pro rely on workflow history instead. Use source control and environments, checked Oct 12, 2026
- Self-hosting upkeep. n8n recommends updating self-hosted instances at least once a month and testing updates in a separate environment; on n8n Cloud, security and stability updates apply automatically. Update n8n, checked Oct 12, 2026
- License & paid tiers. The Community edition leaves out SSO, projects, sharing, environments, external secrets, log streaming, and Git version control. The license limits it to internal business, non-commercial, or personal use. Compare editions, checked Oct 12, 2026