“as a self-hoster, n8n locks too many things behind the paywall - it should've sticked to paywalling integrations with enterprise software like Jira etc. (which I guess they also do?), not OIDC.”
“Tools like n8n, Zapier, and Make exist to connect the apps a business already uses, so information can move between them automatically based on rules you define.”
“I work in big tech and never understood the appeal of n8n. Literally never felt the need to use it at all. I’d see some of our non-engineering folks preach their complex n8n flowcharts and find it amusing.”
“I'd argue the only difference that remains is the visibility and transparency that n8n offers to the process. You can see how it works, and you can see where it fails.”
“Yeah i used to have n8n run workflows to convert my downloaded files into certain formats and rename them according to convention. Works perfectly well. I eventually switched to CI based scripts to have more control over the code customisation but n8n was more than capable if you know what you are doing with it.”
“I was deep into n8n for a solid stretch self-hosted setups, complex workflows, the whole thing. Felt like it had real momentum for a while. Now it barely comes up in conversations unless someone specifically asks about it.”
“It wasn't really worth exploring last year either.For your use case n8n may be a good fit, and Claude or Codex will be happy to set it up for you.If you want this "messenger interface with computers for the agents" feature set Grok Bot is quite good and effortless to use.”
“There's an n8n MCP - literally get Claude to search for the best n8n MCP and have it configure it, then tell it the workflows you want. I've literally got CC setting up some workflow automations for me right now.”
“If you can swing the oracle free tier I'd just move it over there, the ARM instance handles n8n way better than you'd expect and you don't gotta deal with HA's reverse proxy quirks”
“Splitting the 24 hr procedure reminder and the aftercare/review flow into separate sub-workflows makes error handling way easier to manage in production. I build heavy n8n backends daily and running the aftercare trigger on a delay node can get messy if an instance restarts, so pushing those downstream triggers to a dedicated cron or queue state keeps it from dropping patients.”
“**For those who have run both: is it better to keep n8n inside HAOS on local hardware, or is running a dedicated Docker instance on a free cloud VPS the cleaner, more reliable path?**”
“n8n now lets you describe a workflow and AI builds it for you, replacing the blank canvas drag-and-drop process with a describe, review and adjust loop before going live.”
“But for someone who doesn’t code, tools like n8n, Make, and Integrately are a pretty big deal because you can connect different apps and automate workflows without knowing APIs or writing code.”
“None of this is complicated once you know it. It's just that almost every n8n whatsapp tutorial stops at "it works in test mode," and everything above is what sits between that and something you'd actually put in front of a client.”
“The number of options inside n8n is almost limitless. With @bot creating the workflows, managing the webhooks, and Pushover notifications to me, it feels like an instant”
“this is the single best cost optimization tip in n8n and almost nobody does it. the pattern is: use a cheap fast model like haiku or gpt-4o-mini for extraction, classification, and data transformation steps, then reserve the expensive model for the final synthesis or decision step.”
“I can use a curl command and get a response when I get collections from the local instance, but for the life of me I cannot connect through the Qdrant Vector Store node.”
“I think optimizing n8n workflows with multiple AI steps requires assigning different models based on task complexity rather than using a single model throughout.”
“the n8n side can get a little messy if you're trying to build your own webhook layer on top of a tool that wasn't really designed for it tbh. it kinda depends on how much you want to maintain yourself vs just having it work out of the box”
“The connectors are probably the biggest reason I’d use something like n8n. Even if you can code the workflow itself, not having to build and maintain every integration can save a lot of time.”
“Set up a Gmail/Outlook trigger node in n8n on that inbox, filter by sender/subject, then parse the lead info out of the email body (a regex or a small AI node works well here). From there you route it into your CRM/sheet/whatever like any other lead.”
“In n8n you just take the OpenAI Chat Model node and change the base URL to point at Zai, pick the model, done. Small, runs fast and the context window is the thing there, it was eating a lot per run and it did not fall over on the big job.”
“once you're doing entity resolution or deduplication against more than roughly 10k records, n8n's in-memory handling becomes a real liability fast. we hit this at around 80k company records where a Function node was timing out and the DB node couldn't handle the join logic we needed.”
“The cheap hack that a surprising number of agencies actually run on: LSA sends lead notification emails. Gmail Trigger in n8n, parse name, phone and service out of the body. Fragile if Google changes the template, but it works today and takes twenty minutes.”
“That could replace parts of the Supabase-backed application layer, the custom dashboard, and some of the n8n glue. It still wouldn’t replace streaming ingestion, bulk sanctions matching, or replay infrastructure, though.”
“Standard n8n workflows work great for moving a row from Typeform to Google Sheets, but they break down when processing gigabytes of raw data or handling complex, multi-source state machines.”
“Do you immediately start working in n8n, or do you first map out all the processes that the pain points occur in? Or do u do some kind of other documentation/project management”
“We’ve done flows with Bland where a call can gather information, work through a few different directions and take an action before it’s finished, so tying that back into everything you already have in n8n could get pretty deep. Nice build man!”
“Talked to someone in the n8n space recently who does this by default now: after any write node (Sheets, Postgres, Airtable), he adds a read-back check before marking the workflow as done.”
“This isnt a bug, it docker design, as n8n is running inside a docker container, and a container has its own isolated filesystem, it CANT see the files on your pc.”
“I take it the file is in your host filesystem and n8n is looking in the Docker container. Therefore you need to map a volume from your host into the container.”