“Daily Postgres dump off-box (S3 or Backblaze) plus a weekly workflow JSON export to a private git repo. Keep the n8n encryption key in a password manager, not on the VPS.”
“In n8n I need 5 minutes to set up a flow that reads my google calendar and gives me an AI summary every morning. In a custom coded automation, the google account connection alone would take much longer (in n8n, that connection probably already exists from old workflows), same with the AI stuff etc. Then maintainability.”
“The backbone of my openclaw and home assistant is still powered by n8n. Keeps the integration estate separate to the agents. Makes separation of concerns clear cut.”
“There are some niceties that n8n provides such as building block RAG pipelines, etc, but overall it’s basically a UI over a rudimentary programming language plus an LLM SDK.”
“I don't think n8n disappeared, tbh. Claude/GPT made a lot of the simpler workflows easier to build, but once you start connecting multiple apps, handling triggers, retries, branching, etc., you still need something like n8n. AI might be eating the “how do I automate this?” part, but the actual workflow plumbing is still there 😂”
“But from my own experience, once a workflow gets big the canvas turns into a mess of nodes and it's honestly hard to trace what's going on or debug it. I found just writing the same automation in code (or getting Claude to scaffold it) way easier once things got complex, it's linear, you can read it top to bottom, and it's easy to version control.”
“What made me migrate is the fact that my Go codebase gets typechecked entirely with every update but the n8n stuff lives separately and is just prone to bugs. Refactoring it as the project evolves is just super annoying.”
“I just a built a node for it, from simple boolean to route by confidence have a look at it .. [https://github.com/vibe-with-me-tools/n8n-nodes-jev](https://github.com/vibe-with-me-tools/n8n-nodes-jev)”
“i studied and did it a month ago. then got tired monitoring it. so i asked chatgpt to just create me an automated app that i can start, pause and edit in one click, even telling it to monitor. then voila, n8n gone.”
“n8n feels useful once the workflow has enough ugly edge cases that a single API call is no longer the real problem. I’d keep one small workflow in it for a month and check whether it actually saves time before moving more of the stack over.”
“If you mean entering a username and password like a normal browser session, n8n doesn't do that out of the box. The standard and safe way is authenticating via OAuth2 through a Meta Developer App, which connects n8n directly to the Facebook Graph API.”
“If you're just trying to pull some data or post to a page, the HTTP request node with Facebook's graph API is the way to go. Facebook's login flow is a nightmare to automate inside something like n8n because of 2FA and session cookies.”
“I originally thought I’d use n8n mostly for simple app-to-app automations, but I’ve found that the smaller workflows can sometimes be the ones that stick around.”
“The interesting model is plugging an n8n workflow into a system that already has demand. For example, an API/marketplace sends an event → your workflow processes/enriches it with AI → the result is delivered automatically → you charge per use.”
“A better n8n design is a low-touch productized workflow with recurring value: monitor a costly event, generate an actionable alert, and charge for continued coverage. Validate it manually with five users before automating fulfillment.”
“n8n on your own machine can read your list of leads, drop each row into a template, and fire off emails on a schedule for free. The catch is that "local hosted" also means it only runs while your machine is on and awake, so if this is meant to run daily without you babysitting it, that's the first thing to fix, not the sending part.”
“for small workflows, nifty backends, pipelines, special tooling flows n8n still shines. if you combine agents with n8n, then there's nothing stopping you back. with code its 10 times easier to scale, test, deploy and keep iterating.”
“So the whole thing is one n8n workflow: a queue (Sheet or Data Table) with text, status and a scheduled time; an LLM node that drafts from a theme list and never publishes without a status change; a Graph API node that posts; and a token-refresh step, because a long-lived Page token still dies after about 60 days and that is where these setups fail quietly.”
“The n8n workflow part is what caught my eye since most newsletter summarizer tools just run a cron job or lambda, but routing it through n8n means people can tweak the cleanup steps without touching code”
“Where n8n earns its keep is the routing: catch the webhook, write the transcript to where each client expects it (Drive folder, CRM, email), and attach the recording link. Build the client deliverable from that payload and you're done, no re-asking the platform.”
“i think the real skill is learning how to map the business process before touching n8n. once you understand the inputs, bottlenecks, exceptions, and desired outcome, choosing between simple rules, apis, or ai becomes much easier.”
“Better pattern: use a workflow tool (n8n, Logic Apps) for the deterministic steps, and call the agent only for the reasoning part, classify this alert plus similar cases and propose a solution with a confidence score. Keeps the agent narrow and testable, and lets you add human review below a confidence threshold.”
“Reproduce a bug, run migrations, open the page in the browser etc.Workflows can be started by triggers (Jira tickets, GitHub issues, PRs..) and can run across all projects at once, mixing AI agent steps with deterministic steps, similar to n8n.Knecht is in beta and I am looking for people who maintain many projects.”