“Most devs who need custom n8n nodes will just write them manually since they already know the API theyre integrating and the AI-generated code still needs review anyway.”
“if you can code n8n make are slower for complex logic but they win on three things non-technical stakeholders need visual debugging you see the data flow at each node no console.log spelunking built-in auth oauth tokens refresh handled no token management code handoff a pm can read the workflow they cant read your python script”
“There are too many ways to create a token, and I have an app for creating an Instagram bot; however, the tokens provided by the app itself are short-lived. In Meta Business, I generated a token that never expires, but when I try to use it in my flow, I get error #3”
“a no-Ai n8n flow still leans on external state: an api that quietly changes a field, a rate limit, pagination that returns rows in a different order, a webhook that fires twice. the transform is deterministic, the environment it runs in often isn't.”
“1/collaboration, you share a visual business process 2/control, you can access logs, monitor the system 3/centralisation, it runs in one place, easier maintenance”
“And if you don't wanna go through the process of building the flows yourself, use n8n-as-code extension with cursor and vibe code the flows how much ever you can”
“for me the value wouldn't be replacing code, it's replacing all the boring stuff around it: auth, triggers, retries, schedules, execution history and connectors.”
“I'd actually use them together.Let AI help build the logic, then use n8n when you need that logic to run repeatedly, connect multiple services, handle failures and give you something visual that you can monitor and maintain.”
“With n8n, you can actually see how data moves through the workflow, add conditions, handle errors, connect different APIs, and decide exactly where AI should or shouldn't be used.”
“Where it flips: the moment something has to run unattended in production and touch business data. At that point you're not really comparing "script vs n8n," you're comparing "script + logging + retry logic + error handling + a way for a non-technical teammate to see what happened + an audit trail you have to build yourself" vs "n8n has execution history and retries built in."”
“N8N is still best for massive data needing one by one analysis, scheduled runs, and non AI related output use cases (fetching B2B data for example). If you need to run workflows across thousands of rows and need to maintain high quality output for each, N8N is best for this.”
“The setup that usually works best is hybrid: n8n/Make as the orchestrator (triggers, connectors, retries, monitoring) with the gnarly logic in a code/function node. You get the platform's plumbing plus real code where it matters, and you avoid the "drag-and-drop only" ceiling.”
“Yeah it’s bunk if you script well and can orchestrate some with a server. Aside from N8n and zapper click ops type workflow tools, SOAR and IaaC tools often have you just resorting script modules.”
“The one thing that keeps pulling me back is the connectors. Setting up auth for Gmail or a CRM by hand is annoying, and these tools just hand it to you.”
“As a non technical entrepreneur that spend a LOT of time automating my work, I ditched n8n earlier this month, and made codex built the same infrastructure on a VPS.”
“We run 130+ n8n workflows in production at our MSP, and the killer feature isn't any one node — it's that n8n is the glue between tools that were never designed to talk to each other.”
“When I build an n8n workflow I know exactly what the agents are doing. I trust the agents because I built them. There is full accountability and full transparency.”
“For client work the thing that decides it for me is whose account the credentials sit in. On their own n8n instance the Meta and Google tokens belong to them and offboarding me is one password change, whereas with a pile of scripts I end up still holding tokens for a business I stopped working with a year ago.”
“No reason to stick with n8n but if you don’t want to manage infrastructure that could be nice. If you’re willing to self host the workflow orchestrator, there’re good open source options such as Temporal or Dagu.”
“Claude wrote a bunch of n8n automations for me that doesn't use tokens after they've been programmed. There's a degree of overlap for some use cases but generally different tools to get different types of jobs done.”
“I tried to get into n8n maybe like 2 years ago, but I got turned off by the limitations of the OSS version. Also as a developer I like code, so no-code is a turn off for me.”
“Any repeatable deterministic actions or processes should be built out in n8n so they can be executed extremely cheaply, as opposed to having a coding agent do it, where you are burning through thousands or even millions of tokens in the process every single time. Then you just set up an agent to monitor, diagnose, troubleshoot, and report on a regular basis.”
“My plan is to use Claude to make the n8n workflow. Have OpenClaw check in on it from time to time and fix it (because I don't have Claude on a machine that is always on).”