n8n Problems & Issues
Developer ToolFair-code workflow automation you can self-host or run in the cloud
Powerful and cheap (free self-hosted, per-execution cloud billing), but the learning curve is steep, self-hosters own security patching after a run of critical 2026 CVEs, memory crashes and webhook/proxy misconfigurations are common, and cloud support is slow.
Should you use n8n?
Try with cautionn8n works for some teams, but users report recurring problems (score 64/100). Most reported issues: n8n is too hard for non-technical users; Critical n8n security vulnerabilities on self-hosted instances; n8n runs out of memory on large data and files. Not a good fit for: Non-technical marketers and ops staff; Teams without anyone to maintain servers. Users most often switch to Zapier, Activepieces, Pipedream.
Top problems
- n8n is too hard for non-technical users
- Critical n8n security vulnerabilities on self-hosted instances
- n8n runs out of memory on large data and files
Good for
- Developers and technical teams
- Automation agencies and freelancers
- Teams building AI agents
Avoid if you are
- Non-technical marketers and ops staff
- Teams without anyone to maintain servers
Common alternatives: Zapier, Activepieces, Pipedream
Overview
n8n is a node-based workflow automation platform for connecting apps, APIs and AI models, with a visual editor plus JavaScript/Python Code nodes. It can be self-hosted for free (Community Edition) or used as a paid cloud service billed per workflow execution. It is aimed at technical teams, developers and automation agencies who want more control than Zapier or Make offer.
n8n Not Working? Common Errors & Fixes
Step-by-step fixes for the errors users hit most.
n8n Webhook Not Registered (404 Error)
The 404 'webhook is not registered' error almost always means you're calling the test URL when no test is listening, or the production URL while the workflow isn't active/published. Use the /webhook/ production URL and activate the workflow.
n8n Webhook URL Shows localhost
On self-hosted n8n, webhook and OAuth URLs show http://localhost:5678 when n8n doesn't know its public address. Set WEBHOOK_URL (and N8N_HOST/N8N_PROTOCOL) to your public domain and restart.
n8n Out of Memory (JavaScript Heap Out of Memory)
n8n crashes with 'Execution stopped at this node (n8n may have run out of memory)' when a workflow loads too much data at once. Process items in batches, move heavy work into sub-workflows, and on self-hosted instances raise the Node.js heap limit.
n8n Connection Lost Error
'Connection lost' in the n8n editor usually means the browser's push connection (WebSocket) is blocked by a reverse proxy or rejected for an origin mismatch. Add WebSocket upgrade headers to your proxy and set the public URL and proxy hop variables.
n8n Executions Stuck in Queued / Starting Soon
Executions stuck in 'Queued / Starting soon' mean no worker is picking them up. On self-hosted setups, fix mismatched queue-mode settings or restart workers; on n8n Cloud, restart the workspace or contact support.
n8n Google OAuth redirect_uri_mismatch Error
Google rejects the connection when the redirect URI n8n sends doesn't exactly match the one in your Google Cloud OAuth client. Copy the redirect URL from the n8n credential into Google Cloud, set your public URL on self-hosted instances, and update n8n if you're on an affected version.
n8n Schedule Trigger Running at the Wrong Time
n8n schedules use n8n's own timezone setting, not the server clock, and default to America/New_York. Set GENERIC_TIMEZONE for the instance and check each workflow's timezone setting, which overrides it.
n8n 'Cannot Read Properties of Undefined' Error
This error means a node or Code node tried to read a field from data that doesn't exist, often because a previous node returned nothing or a different shape. Inspect the input data, guard against empty items, and make sure workers run the same version.
n8n Workflows Broken After 2.0 Update
n8n 2.0 introduced many breaking changes: Code nodes run on task runners and can't read env vars by default, Execute Command is disabled, the Start node and Pyodide Python are gone, and Activate became Publish. Check the official breaking-changes list and re-enable or rewrite what you need.
n8n Cloud Workspace Offline (503 Error)
A 503 'Workspace offline' page means your n8n Cloud instance is down or restarting, often after running out of memory or during an incident. Restart the workspace from the Cloud dashboard and contact support if it doesn't come back.
Signals & Issues
Patterns extracted from real user feedback — not raw reviews.
The most common complaint on G2 is a steep learning curve, especially for people unfamiliar with APIs, JSON and branching logic. Advanced workflows often need JavaScript in the Code node, which undercuts the no-code pitch.
Free self-hosting means you handle reverse proxies, WebSockets, backups, Postgres, upgrades, monitoring and your own OAuth apps for Google or Slack. Losing the encryption key makes stored credentials unusable.
Six critical CVEs were disclosed between January and March 2026, including CVE-2026-21858 (unauthenticated remote code execution on internet-exposed instances), and an October 2026 bulletin covered eight more, five rated High. Self-hosters must patch quickly and keep instances behind a reverse proxy.
Big JSON payloads, binary files, Code nodes and manual test runs can exhaust memory, producing 'Execution stopped at this node (n8n may have run out of memory)' or 'JavaScript heap out of memory'. n8n's own docs recommend batching, sub-workflows and more RAM.
Several community threads describe Cloud executions stuck in the queue for hours or days, often after an execution spike, while the UI shows no active executions. Fixes usually require a workspace restart or contacting support.
Many users hit 404 'webhook is not registered' errors because n8n has separate test and production webhook URLs and the production one only works while the workflow is active/published. Self-hosted instances behind a proxy also show localhost URLs until WEBHOOK_URL is set.
Version 2.0 removed the Start node, Pyodide Python Code node, MySQL storage and in-memory binary mode, blocks env var access in Code nodes, disables Execute Command by default and replaces Activate with Publish. Self-hosters who updated without reading the breaking-changes list saw workflows fail.
Trustpilot 1-star reviews (37% of 49) mostly cite email-only support, slow replies and account lockouts with no recovery path. Community forum threads describe cloud workspaces offline for days with no ETA. Self-hosters on the free edition get forum support only.
Users report blank errors and generic messages such as 'Cannot read properties of undefined' or 'Connection lost' that don't point to the cause. G2 reviewers ask for better debugging tools.
Reviewers say the canvas gets unwieldy as workflows grow, and G2 users mention slowness compared with other apps. Splitting logic into sub-workflows is the usual workaround.
Connecting Google Drive, Gmail or Sheets often fails with redirect_uri_mismatch, both on self-hosted instances using localhost URLs and on n8n Cloud, where users reported a mismatch between the displayed and sent redirect URL that was fixed in a later release.
Cloud Starter and Pro are cheap, but SSO, Git version control, multiple environments and queue mode sit in the self-hosted Business plan at about €667/month billed annually, with overage buckets of €4,000 per 300k executions. Starter caps executions at 5 minutes and keeps 7 days of logs.
What Users Love
Free self-hosted Community Edition with unlimited executions
The Community Edition costs nothing beyond your server, which makes high-volume automation far cheaper than Zapier or Make.
Billing per workflow execution, not per step
One execution is a full workflow run regardless of how many nodes it has, so complex multi-step workflows cost the same as simple ones.
Code nodes and HTTP Request for anything without a connector
JavaScript and Python Code nodes plus a generic HTTP Request node let developers integrate almost any API.
Strong AI agent and LLM workflow support
AI agent, MCP and LLM nodes are included on every plan, making n8n a popular choice for building AI automations.
Data stays on your own servers when self-hosted
Self-hosting keeps credentials and workflow data in your own infrastructure, important for privacy-sensitive teams.
Highly rated by users who get past the learning curve
n8n averages 4.7/5 from about 295 G2 reviews, with users praising flexibility and reliability once set up.
Pricing Plans
- ✓Unlimited executions and workflows
- ✓All core nodes and AI nodes
- ✓Custom nodes
- ✓Forum support
Limitations: No SSO, Git version control, environments or log streaming; community support only.
- ✓2,500 executions/month
- ✓Unlimited users and active workflows
- ✓5 concurrent executions
- ✓1 shared project
- ✓AI Assistant credits
- ✓Forum support
Limitations: 7-day execution log retention, 1 day of workflow history, 2,500 saved executions.
- ✓10,000 executions/month
- ✓Unlimited users and active workflows
- ✓Higher concurrency
- ✓3 shared projects
- ✓Admin roles
- ✓7 days of Insights
- ✓40-minute max execution time
Limitations: 30-day log retention, 5 days of workflow history, no SSO or Git version control.
- ✓40,000 executions/month
- ✓SSO and LDAP
- ✓Git version control
- ✓Multiple environments
- ✓Queue mode
- ✓30 days of Insights
- ✓6 shared projects
Limitations: Self-hosted only (hosted version on a waitlist); trial requires a credit card.
- ✓Custom executions
- ✓200+ concurrent executions
- ✓External secret stores
- ✓Log streaming
- ✓365 days of Insights
- ✓SLA-backed dedicated support
- ✓Hosted or self-hosted
Features
Deployment
- Self-hosting
Free Community Edition via Docker or npm
Core
- Visual workflow editor
- Sub-workflows
Developer
- JavaScript Code node
Runs on task runners since 2.0
- Python Code node
Native Python requires external task runners since 2.0
AI
- AI agents and MCP
Included on all plans
Triggers
- Webhooks
Separate test and production URLs
Scaling
- Queue mode with workers
Business/Enterprise for licensed use
Collaboration
- Git version control and environments
Business and Enterprise only
Security
- SSO / LDAP
Business and Enterprise only
Platform
- Mobile app
Web editor only
Who Should Use This?
Good Fit
Developers and technical teams
Code nodes, HTTP requests and self-hosting give full control at low cost.
Automation agencies and freelancers
Per-execution pricing and self-hosting make client automations cheap to run at scale.
Teams building AI agents
Native AI agent, LLM and MCP nodes are included on every plan.
Privacy-sensitive organizations
Self-hosting keeps data on your own infrastructure, but you must patch security releases promptly.
Neutral
Small businesses with some technical help
Cloud Starter is affordable, but expect a learning curve and slow support when something breaks.
Avoid
Non-technical marketers and ops staff
JSON, expressions and Code nodes are hard without API knowledge; Zapier is easier.
Teams without anyone to maintain servers
Self-hosting requires proxies, backups, upgrades and security patching; use n8n Cloud or a managed tool instead.
Regret Patterns
Common buyer's remorse scenarios reported by users.
Non-technical users expect no-code, then find that data transformations and edge cases need Code node scripts and expressions.
Proxy, WebSocket, OAuth, backup and upgrade issues consume hours that outweigh the subscription savings.
Self-hosters running internet-facing instances had to rush updates after critical CVEs were disclosed in 2026.
Pulling the latest image without reading breaking changes (notably 2.0) disabled nodes and broke Code node behavior.
Cloud users report workspaces offline or executions stuck for days while waiting on email support, with clients affected.
Teams that grow into needing SSO, environments or version control find those features only in the much pricier Business plan.
When It Breaks Down
Scenarios where this product tends to fail users.
Memory spikes cause 'n8n may have run out of memory' errors unless data is batched and split into sub-workflows.
Missing WebSocket upgrade headers or wrong N8N_PROXY_HOPS cause 'Connection lost' and 'Invalid origin' errors in the editor.
Bursts of executions can leave runs stuck in 'Queued / Starting soon' until the workspace is restarted.
Breaking changes like those in 2.0 disable nodes and change Code node behavior.
Starter caps executions at 5 minutes, so long AI or scraping jobs fail unless you upgrade or split them.
You need your own Google Cloud OAuth app, and a wrong public URL produces redirect_uri_mismatch errors.
Alternatives Users Switch To
Zapier
9x mentionedMuch easier for non-technical users and has the largest app library; trade-off is far higher cost at volume, linear workflows and no self-hosting.
Make
9x mentionedVisual scenario builder that is friendlier than n8n with good value pricing; trade-off is cloud-only and a credits model since 2025.
Activepieces
5x mentionedOpen-source, self-hostable and simpler than n8n for business users; trade-off is a smaller integration library.
Pipedream
5x mentionedCode-first automation for developers with managed hosting, so no servers to maintain; trade-off is less visual editing.
Microsoft Power Automate
5x mentionedBest fit for teams already on Microsoft 365; trade-off is weaker support for non-Microsoft apps and complex licensing.
Frequently Asked Questions
See how n8n compares in our Best Automation Software rankings, or calculate costs with our Budget Calculator.
Work at n8n or spotted something outdated? Suggest a correction — we verify every change against public sources. See our methodology.