“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.”
“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.”
“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.”
“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.”
“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.”
“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've been using n8n for a while and haven't noticed anything catastrophic on my end, but i'm also not on twitter so maybe i'm missing the drama. 740k views is wild though, that's not just a few power users complaining”
“The reliability part is underrated. Claude Code/Cursor is great for writing a one-off script, but a script doesn't have a webhook listener sitting there 24/7, doesn't retry on failure, doesn't have a visual execution log you can check when something breaks at 3am, and doesn't let a non-technical teammate glance at the flow and understand what happens.”
“I made mine took me around 2 weeks and I self hosted n8n and chatgpt,claude,Gemini free versions help me understand the node stuff, I use Google studio free tier for my setup, it gets my complete office work done muaaaa”
“that's a solid workflow. i'm curious, did you run into any particular headaches with the PDF generation itself, especially with formatting across different data sets?”
“i used to use n8n quite a bit building for businesses and myself, it’s been a little while since i’ve used it but i’d love to hop on a call and see if i can help”
“On n8n 2.x I also hit multipart/form-data problems talking to Gotenberg (415/500). A small local proxy that accepts JSON { html } and forwards to Gotenberg with curl fixed it for me.”
“Tracking threshold duration based on historical patterns is brilliant way, cleaner than getting spammed with false positive alerts during expected quiet windows. Do you handle that time tracking state inside n8n directly (like updating a Redis/data store key on each run), or just querying the execution history table to calculate the gap?”
“N8n is reliable, workflows are easily created with Claude Code ( and the appropriate skills ), tons of maintained connectors available, and it's much more secure than an agent with keys stored in a text file.”
“I have said it many times, automation like N8N great for starter and test the concept, especially it already have many built-in 3rd party integration. But once we're going to scale or have advanced function, having it in programming code are more reliable & maintainable like FastApi or any API that we develop traditionally.”
“N8n is great for quickly hacking something and putting it in production but then when it grows is a mess to maintain, slow, fragile, expensive to run.”
“I still use N8N, but only for small things. It's now pretty easy to automate things with AI coding. Though N8N does provide some additional benefits like logging, re-execution of failed workflows, etc..”
“You’re ignoring that n8n and other low code tools are defined in structured markup files (text). Models can generate those just as easily while still providing the human the top-down “at a glance” visual presentation of structure and functionality.”