“Building the workflow takes an afternoon. Owning it for a year is the actual job, and that part looks the same whether you used n8n or wrote the script yourself. The question is whether you want to be the person who gets called when it stops at 6am.”
“The script version works great until it fails. Then someone has to find out what failed, where, and how to re-run it and that's the part n8n was actually doing for you.”
“the pricing jump is what keeps me on self hosted. if you're already comfortable with docker it's not much overhead and you dodge the scaling costs entirely”
“n8n is certainly worth it. If you look on YouTube, you will see many content creators promoting the idea that n8n is an outdated tool—suggesting you should abandon it in favor of others like Claude—but the reality is that it remains one of the most powerful tools available.”
“Saw complaints about sequential processing being slow (500 items = 15 min) and execution pricing climbing fast (€24/mo to €800+). Self-hosting fixes it but adds overhead.”
“I am leaning heavy on Postgres and have handed off some of the n8n to actual scripts as not to slow things down. Right now, I am about to launch - just waiting on my LLC, EIN, bank, stripe.”
“I use N8N for what it is and Inngest for similar purpose. My $200 claude code or $200 chagpt doesn't do the job N8N does. I'm hoping to retire N8N ($60 sub) in a few months since i'm paying $99 for Inngest.”
“If you’re making a full app it doesn’t make much sense to even have n8n in the loop. Like someone else said it’s an orchestrator it already has a UI.”
“For the average user n8n is way better and cleaner than anything Claude can do with coding. If something doesn’t work the user can debug by click through nodes to understand what went wrong. If Claude made a mistake in the development it is pretty hard for the average user to identify the issue.”
“i'd keep n8n strictly in its lane, automation and orchestration. the moment you start treating it like a backend, things get messy. your webhook hits n8n, it does its processing dance, and then fires the result somewhere your app can actually use.”
“A node that runs, returns an empty array and goes green is present in the run data with a success status. Nothing is absent to alert on and no branch went the wrong way.”
“I've found it's much more efficient to keep all of my many automations centralized under one roof and not have to manage a bunch of webapps and docker containers all over the place.”
“this is such a nasty silent failure mode in n8n. ive been bitten by empty array outputs where the rest of the flow just evaporates without throwing an actual error so now i always route false branches to a dead man alert node.”
“this is cool, i worked on something similar for monitoring our internal tools but never thought to use n8n for the orchestration part. was always just cron jobs and custom scripts”
“Was unable to sit up on Qnap. NAS. After troubleshooting with Claude and ChatGPT, both said that the current Qnap OS does not support what n8n wants for chat bot infrastructure.”
“I think one thing that keeps me with n8n is being able to have clearer error logs when running things overnight. And if I'm building something for a client, it helps alot”
“I recently wired the n8n MCP to Claude and I use Claude Code to build and test my n8n workflow. It has taken development time of complex workflows from days to under an hour”
“We’ve moved almost all of our flows into N8n and rely on “AI” for very little. Clear controllable boundaries at each layer with direct control over the exact information and almost no room for hallucination.”
“N8n is extremely good for visualization complex workflows and breaking them down to small steps. Try that with a codebase generated entirely by claude”
“I still prefer n8n because it’s easier to make changes and troubleshoot with nodes. Much more difficult if you have to go through (or have Ai go through) that much code to fix a simple error in a node. Also everything feels so much more organized in n8n with credentials, integration, etc..”
“Been running an n8n automation for a restaurant client where customers message the Telegram bot and it doesn't just spit back a canned menu, it actually holds context and personalises replies based on what they ask.”
“n8n did fix the "web of routers I can't explain to anyone" problem, mostly because it's closer to actual code with a UI on top than either zapier or make, so at least the branching logic reads like branching logic. what it did NOT fix on its own: a response-handling setting that silently serialized a payload in a way a plain request never would've, so something that tested clean by hand broke in the actual runtime and only in that runtime.”
“A workflow can look completely healthy in n8n WHILE the actual platform action stops happening. smh - did you end up adding any recurring health checks on the META side, or are you mainly relying on delivery status/webhooks to catch this now?”
“The Gotenberg multipart pain is honestly why I ended up building DocsAutomator, so weigh accordingly. Instead of maintaining invoice HTML plus a PDF service plus a proxy, you design the invoice as a Google Doc with {{placeholders}}, and n8n makes one call with the row data and gets the finished PDF back.”