Dropped n8n after coding alternatives to avoid license execution limits → custom code
“even their highest enterprise license was cutting it close”
n8n alternatives: where its users went, and why they left
n8n (n8n.io) has 39 sourced reports on Friction, drawn from 80 public source threads (as of 2026-10-15), 5 of them describing a move away. This page reads them for one question: if you are leaving n8n, what do its users say they moved to, and what pushed them out?
Get started free with your email Open n8n on Friction
Where n8n users say they went
Switching reports that name a destination. A count is the number of reports naming it, not a market share: Friction only holds what people say in public.
| Named alternative | Reports naming it | Newest report |
|---|---|---|
| Node-RED | 2 | 2025 |
| GPT-4o | 1 | 2026 |
| Custom Code | 1 | 2025 |
| Compose AI | 1 | 2025 |
| Custom Code-First Workflow Engine | 1 | 2025 |
| VoltAgent | 1 | 2025 |
| Trigger | 1 | 2023 |
In their words
Brittle, tightly coupled workflows push user toward an agent-based alternative → Compose AI
“They're deterministic but brittle and not adaptive. The tight coupling means one change breaks everything”
Hit the limits of n8n-style no-code when customization and control were needed → VoltAgent (code framework)
“as soon as we needed customization and deeper control, we hit the limits of no-code tools”
Slow visual-tool execution and custom scripts led developer to a code-first engine → custom code-first workflow engine
“workflows that required custom scripts within the visual tools, dealing with 3-5 second execution times”
What pushes people away from n8n
The most-reported open problems, worst severity first. Each links to the item with its source.
AI Agent node breaks on a simple OpenAI call after upgrading · Reliability & bugs · Blocks work · 4 people
“But when I try to edit any workflow (even a newly created one), this error shows up”
Editor websocket fails behind nginx reverse proxy after upgrade · Self-hosting & upgrades · Blocks work · 3 people
“Error connecting to n8n Could not connect to server. Refresh to try again”
Extract From PDF node runs out of memory on a small file · Reliability & bugs · Blocks work · 3 people
“When running a workflow with the Extract from File node and selecting the operation Extract From PDF, the execution stops unexpectedly with an out-of-memory error”
MCP tool calls fail with new toolCallId and old workflows stop running after update · Reliability & bugs · Blocks work · 2 people
“MCP tool calls are failing due to new toolCallId, previous n8n worfklows won't run on update to most recent version!”
MCP Client Tool errors with any Gemini model but works with GPT-4o · Integrations · Annoyance · 4 people
“Since updating to the 2. version we have a lot of issues with Agent Nodes using the Gemini models”
Other workflow automation tools on Friction, and what their users struggle with
Switching trades one set of problems for another. The same evidence, for each tool Friction covers in this category:
Windmill
17 reports · 69 source threads · most-discussed area: Reliability & bugs
Temporal
14 reports · 65 source threads · most-discussed area: API & developer experience
Counts and reports reflect people who post in public (developers and technical buyers are over-represented). A tool with fewer reports is not a better tool; it may only be discussed less. How the data is built.