n8n

“Awesome! Very cool to have this natively in n8n”

“n8n is great until you need to replay a run, write a test, or retry something that is not a checkbox, and at that point it is code. for a non tech client who only cares about output, start on the platform and move only the one flow that keeps breaking, that flow has already told you it needs real error handling.”

“when should you decide work with automation website like retell or n8n or zapier to make your agent and when you decide move to code it?”

“Has a Zapier/Make/n8n workflow ever silently stopped running on you? How did you find out?”

“wow that's cool, without your permission 😂 will copy some ideas into my Wassenger based n8n workflow too 😄”

“that's almost always a test-vs-production webhook mismatch, not an n8n bug. The Active toggle needs to actually be on (separate from "published"), and whatever URL you registered with Meta's WhatsApp API has to be the production webhook, not the one you get while the editor's open.”

“On #1, this is almost certainly the one-webhook-per-app thing. Meta only allows one webhook subscription per app, so the test URL and the production URL keep overwriting each other.”

“Congrats on getting it working end to end, that's honestly the hardest part.”

“I've messed with n8n enough to probably point you in the right direction”

“Pin the image tag. A compose file with n8nio/n8n:latest restores onto whatever version is current that day, and if that's a few releases ahead of your dump you get a database migration in the middle of your recovery. Keep the exact tag in the compose file and bump it only on purpose.”

“You don't need a dedicated app for this; the row-to-invoice flow is a clean n8n or Make job.”

“n8n still on demand.*”

“n8n records both as successful executions, because they are. So "this comment never got a DM" and "everything worked" look identical in your executions list.”

“most providers expose that as one call, so make or n8n can do it with a plain http node without a dedicated integration.”

“n8n ist ein komplett anderes Skillset: kein ML-Verständnis nötig, eher "Logik verknüpfen" statt "Modelle trainieren".”

“Ideally it would plug into Make, Zapier or n8n, let you pick a clean invoice design, and sign and send the PDF in the same flow. Is there any app or API that already does all of this well, or are you all still stitching it together manually?”

“Bro n8n is literally archaic as is. Kind of useless and built for entry level devs”

“Basically FreshRSS + n8n (or something home made) + a small vector database. Main collector pulls stuff in, chunks it up and puts it in the vector db for similarity search and then bundle them all up to another pipeline to generate a "report" or "newspaper" based on all that, essentially a curated list.”

“Full template's linked below on the n8n Hub if you want to see how it's wired.”

“Try n8n and just compare. BTW, I’ve built https://n8n-challenges.app so you can practice there.”

“If you want to make money then you need a good use case that automation can solve and you invest 20-30 hours into learning n8n and webhooks.”

“Should I continue learning ML or start with n8n?”

“You can try n8n workflow with RSS trigger, then pipe items to local LLM for dedup and summarization, output to email or simple web UI. Not a ready made app but works okay”

“In n8n specifically, I'd make each adapter its own sub-workflow (Execute Workflow node), called from a parent that loops over platforms. Keeps auth, pagination, and rate-limit handling isolated so one platform's API changing doesn't touch the others.”

“honestly the cleanest thing ive found is writing a tiny middleware service that handles all the oauth crap and spits out normalized json, then n8n just calls that one endpoint. each platform still needs its own auth flow obviously but at least the workflow nodes stay simple.”