What people previously said about n8n

“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.”

“What stayed in n8n after that was anything with a lot of third party auth. Rewriting OAuth against six APIs just to own the runtime is a bad trade.”

“I like n8n, but I hate using agents to work with it. Claude for me was unusable, limits reached after 2 prompts.”

“I keep all my credentials in n8n and let claude use them for certain projects. This is better for me than. Env files all over the place”

“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”

“I never, ever want to go back to pure script(s) created by claude. It is an incredible tool, but adding n8n on top is a godsend.”

“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.”

“Draw a rough draft of the n8n workflow structure. Take help if you need it — Claude is really good for this.”

“N8n is extremely good for visualization complex workflows and breaking them down to small steps. Try that with a codebase generated entirely by claude”

“n8n is my preferred way of shaping the data my agents reason over rather than hope they use the original sources correctly.”

“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..”

“N8N is more secured on building the connection than your custom codes and you need much Claude effort to make the connection secure”

“That is working as intended in n8n, and it catches everyone once. The status is per execution, not per node.”

“Agentic coding didn't kill n8n, it changed what I use it for.”

“Does n8n self hosting now have the ai chat builder? Haven't fired up my n8n self hosted entity in a while.”

“what's the one thing it does that n8n doesn't, in a sentence? that's usually what tells me whether it's worth moving anything over”

“n8n was great.. but it's time has pass. With agents, it really isn't needed anymore.”

“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.”

“What repetitive workflow do you still handle manually in n8n?”

“Agentic coding has kind of made n8n obsolete”

“n8n's Code node makes this a few lines, and you can throw so it routes to the error workflow with the raw response attached.”

“still curious how many of those n8n workflows were actually running in production vs just shared as examples though”

“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.”

“Show HN: Silent Fail, get an email when your n8n workflow stops running”

“This is cool, I've been messing around with n8n for home automation stuff but never thought to tie it into a meal tracker. The Telegram bot angle is smart, way less friction than building a whole app frontend.”

“My name is Elias and I’ve drafted my first n8n workflow (or maybe "revised" is the better word).”

“I've been using n8n in production for a couple of years, mostly on operational workflows that have to cope with the messy stuff: duplicate events, retries, exceptions, human handoffs and processes that don't work the way the SOP says they do.”

“Really? We have less than 5% issues over years of N8N use. I guess security first matters.”

“i self-host n8n and rely on external monitoring, logs, and a simple retry queue outside n8n.”

“use OpenRouter for a free API key, connect that into your n8n workflow so you're not paying anything while you're still learning”

“I stopped using n8n because of licensing and because of the hellish credential hell. Easier to use Composio + Codex.”

“The "97% of n8n workflows fail" stat has no source. We traced it and measured the real numbers instead.”

“Tried n8n self-hosted next because everyone in every thread swears by it - spent a weekend getting the docker container stable, then the webhook auth broke on the first real lead, no idea why.”

“I built a dashboard for n8n workflows—what do you think?”

“Community nodes are the easy one to miss. Put the npm package and exact version in the bundle, since the target instance has to install it separately and n8n warns that an incompatible upgrade can break every workflow using that node.”

“The jump from watching n8n tutorials to actually building a workflow can be confusing especially when you’re trying to figure out APIs, authentication, nodes, webhooks and data mapping at the same time.”

“What should travel with an n8n workflow JSON between instances? n8n's docs say exported workflow JSON includes credential names and IDs, and warn that HTTP Request nodes may contain authentication headers imported from cURL.”

“The biggest n8n learning curve for me would be understanding where the data changes shape between nodes. Logging/inspecting the output after each important step makes debugging *way* easier.”

“I have 4 different daily n8n workflows that push the latest codebase from my Hermes and clients/friends Hermes to their own independent repos on GitHub.”

“I've been using n8n for a while and genuinely think it's one of the best tools for connecting APIs, services, webhooks, schedules, and AI models.”

“For the practical side, every n8n integration is the same three moves no matter which service you're connecting. Credentials first: search "SERVICENAME API key", follow the first result to the developer settings, create the key, paste it into n8n under Credentials before you touch a single node.”

“n8n was extremely expensive for enterprise setup. Now these models can do the same thing at less than 1% of the price that n8n wanted.”

“I've seen the built-in HTTP nodes choke on larger PDFs when Meta's CDN gets sluggish.”

“I'm using wondering if you use n8n to process data from AI via HTTP request node does it remove the hidden watermark? cause I don't know if n8n uses copy & paste or it types like a real human”

“I think that translates to: n8n as orchestrator of all the nodes within the n8n workflow, amongst which agent nodes.”