Good evening, everyone.
Lately, out of 10 leads that come into my WhatsApp, 4 to 5 don't receive the Evo funnel/message.
Does anyone know what the problem might be or has experienced this before?
The scale here isn't large But it's not small either.
Around 600 leads per day divided across 4 WhatsApp groups.
rying to consolidate my n8n stack for social posting across 6 platforms and the integration story is messier than I expected. Wanted to ask before I commit to one.
Here's what I've mapped so far. Blotato has official n8n nodes, works with 9 platforms (TikTok, YT, IG, Threads, FB, X, LinkedIn, Pinterest, Bluesky), $29/mo starter. Handles video uploads which is the big one. Downside is no Google Business Profile and pricing jumps if you need multiple client accounts. Postiz has a community node called n8n-nodes-postiz, open source and self hosted so you own the infra but you also debug it. Great if you want full control, painful if you don't. Simplified shipped an n8n node last year covering 7 platforms including GMB, TikTok, YT, Pinterest, Threads, LinkedIn, FB. No X integration in the node which is a real gap.
The bigger names are worse than I expected. Buffer has a basic n8n node but only supports the older API subset. Hootsuite, Later, Vista Social, SocialPilot have no n8n node at all, you'd be building HTTP request chains for every action. Metricool has an MCP server but no n8n node, so it's only useful if you drive everything from Claude.
Been testing PostFast too since it does n8n plus Zapier, Make, and MCP for Claude and ChatGPT, covers 11 platforms including GBP, €10/mo. Not fully sure yet if the n8n side is a proper community node or HTTP request based, still digging. Cheapest option I've found but the community around it is small so less docs when you hit an edge case.
The gap I keep hitting is TikTok and Instagram Reels uploads. n8n core has no official TikTok node, Instagram is limited to Business/Creator accounts only with a 50 posts per 24hr cap through the Graph API. Every scheduler above hits those same platform limits, they just hide them better.
What I'm trying to figure out: is anyone running a stable n8n stack that hits TikTok, IG Reels, YouTube Shorts and LinkedIn from one workflow without babysitting it?? Blotato looks like the safest bet from what I've found but want to hear from people who've been running it for months. Also open to stacks I haven't come across yet
I have a large n8n workflow, that I am mulling over exporting the json and feeding it to AI so that i may rebuild it as a .tsx. I am thinking it would be cheaper procesing? like its all cloud computation right? having n8n in the loop is just an added step? I have all my n8n workflows self hosted on Google cloud. scalling would be similar? ...idk, i haven't exported a n8n json yet. I feellike i understand n8n better than reading some index.js file. anyone been down this road yet? what has your experience been?
A birthday present kicked this off. My girlfriend got me a 3D printer last year, I taught myself Fusion 360, then I taught Claude to drive Fusion 360 for me. Once an AI was doing the CAD, I wanted to see how far the loop could go, so I pointed it at the content side: could a social account run itself with nobody writing the posts?
I built it, let it go, and it worked well enough that I pulled it out into a standalone n8n workflow anyone can import.
On a schedule it wakes up, decides what today's post should be, writes the caption, writes the image prompt, generates an original image, and publishes to a Facebook Page and its linked Instagram. I do not write anything.
What makes it more than a cron job that posts random stuff:
The account is aware of two things at once.
What it is about (topic-aware).
The whole content plan lives in one Config node: the vertical, the voice, five topics with angles and hashtags, and a 12-slot posting cycle. It is plain data, not hardcoded branches, so retargeting the pipeline to a completely different brand means editing that one node and nothing else.
What it already said (post-aware).
Before it writes, it reads its own recent history out of Airtable and will not repeat a topic it just covered. It also fills the grid in order, which matters because Instagram's grid fills left to right, so grouping a topic lays down a clean row instead of a random mess.
The honest results,
because that is the useful part: I ran it for months, twice a day. Around 11 cents a post (almost all of it the image), so roughly 22 cents a day. It got basically no traction. 149 posts in, the account has 6 followers. That is not the automation failing, it is that Instagram and Facebook both push video and reels with music now, and this posts still images.
I switched it off in June to stop the spend while I move it to a new setup, and the next version will generate video instead. That is a one-node swap (point the image step at a video model), it just costs more like a dollar or two a post.
You can see what it actually made here: instagram.com/agenius3d. Every image and caption there was the workflow, not me.
Stack: n8n, an LLM for the caption and image prompt (Claude Haiku by default, swappable), KIE.ai for the image, Airtable for the memory, and a notify node (Telegram, also swappable).
It is open source (MIT), with the workflow JSON, the Airtable schema, and the docs here: https://github.com/Mfrostbutter/n8n-workflow-templates/tree/main/workflows/autonomous-social-media-pipeline
Happy to break down any piece in the comments: the dedup logic, the grid-cycle math, the image poll loop, or the Instagram two-step publish.
I've been trying to streamline my daily news posting workflow, and this is what I've come up with so far:
Visit a news site (usually BBC or The Guardian).
Copy the latest article and download its featured image.
Paste the article into an LLM (I use Gemini Pro) and have it translated into Bangla.
Repeat this in the same chat for 4–5 different articles.
Open my WordPress site and, for each article:
Upload the image
Paste the translated content
Add the generated headline as the title
Open Canva and use Batch Create:
Add all the downloaded images
Add the corresponding Bangla headlines in the text column
Generate all post images at once
Download the finished graphics.
Upload them to my Facebook page.
That's the entire workflow.
I'm looking for ways to make this even faster or automate more of it. Any suggestions?
Ello!
I absolutely hate writing changelogs. When I'm deep in a coding flow, my commit messages get incredibly lazy ("fixed bug", "optimized file lol", "finally working"). It’s fine for my own speed, but it sucks for anyone else trying to read the project history or see what actually changed
So I spent about 2 hours building an n8n setup to completely automate the boring part straight from a GitHub push webhook.
The whole workflow is open-source. You can grab the JSON blueprint from the repo, host it yourself, and build on top of it: [link!](https://github.com/engyossefyossry-crypto/git-log-humanizer)
🛠️ How it works under the hood:
The Ingestion: It catches the live GitHub push event and grabs the raw commit text array.
The Clean-up: Passes the commits to Llama 3.1 (via Groq) locked behind a strict JSON schema output parser. The model filters out the pure noise (like "finally working") and rewrites the actual technical fixes into clean, professional bullet points categorized by Features, Bug Fixes, and Performance.
The Auto-Commit: It compiles everything into markdown and uses the GitHub API node to automatically update `docs/CHANGELOG.md` in the repo.
The Logs: In parallel, it drops a clean summary into Discord/Gmail and logs the raw metrics to a database table for tracking engineering velocity.
📋 Two details I added to make developing this less annoying:
Local Sandbox Fallback: Testing webhook-driven pipelines usually means spamming your live git history with empty commits just to see if your nodes trigger. I put a small JS check in the ingestion node, if you run it manually in the n8n editor without a live payload, it swaps in a mock array of garbage commits so you can debug the whole canvas instantly without polluting your real GitHub repo.
Deterministic Parsing: Small models love wrapping JSON responses inside markdown code blocks (```json ... ```), which instantly breaks downstream JavaScript or database nodes. The structured output parser fixes this by forcing raw JSON straight out of the inference layer.
It's fully free-tier friendly and easy to configure. Check out the repo, hook up your own credentials, and let me know if you have any ideas to scale it or handle multi-repo setups!
All my community nodes are for removal after last update?
There are a few tools out there that do something like this, but they're closed source, and a couple even send your workflow to a server or an LLM to do the "sanitizing." That kind of defeats the whole point: if you have to hand your private data to someone else in the first step, it was never private. For a tool whose entire job is protecting sensitive data, "trust us, we won't look" isn't good enough.
So I made n8nRedact. Paste or drop a workflow, get a sanitized copy back.
First, the problem. n8n doesn't strip anything on export. Even though your actual credentials aren't in the JSON, a surprising amount still leaks: credential names, cURL auth headers in HTTP Request nodes, Airtable base/table IDs, Postgres table names, Notion page IDs, Telegram chat IDs, hardcoded URLs and emails, your instance ID, and webhook tokens buried inside URLs.
What it does:
- Detects and replaces the sensitive stuff: credentials/keys, emails, URLs, UUIDs and hex IDs, Airtable/DB resource IDs, Telegram chat IDs (string and numeric), phone numbers, instance IDs, and more.
- Format-preserving. john@acme.com becomes user1@example.com, not [REDACTED]. The output stays a valid, importable workflow.
- Deterministic. The same value always maps to the same fake, so cross-node references still line up.
- Side-by-side diff so you see exactly what changed.
- Toggle rules on/off, with live counts of what was found.
- n8n expressions (={{ $json.foo }}) are preserved, not mangled.
Why you should be able to trust it:
- 100% client-side. Nothing is uploaded, and it can't be. There's a Content-Security-Policy with connect-src 'none' that physically blocks the browser from making any network request. Even a compromised dependency couldn't exfiltrate your paste. There's an automated test that fires a fetch and asserts the browser blocks it.
- Open source, so you can verify all of the above instead of taking my word for it.
- Works offline after first load.
Free, no accounts, no analytics, no cookies.
Repo: https://github.com/Shuffzord/n8nRedact
Live: https://shuffzord.github.io/n8nRedact/
Would love feedback, especially edge cases where it misses something or over-scrubs. If you've got a weird node type that leaks in a way I haven't handled, drop an example (anonymized 😉) and I'll add a rule.
Hey :),
I bought a new public domain for my home server and did all the rerouting through cloudflare, but in my N8N workflows, I can't get it to change to the new domain for the webhook url.
I updated the webhook url variable in the docker-compose.yml and recreated the container, but in the telegram nodes, they still have the old webhook url.
I also tried restarting the vm & doing the [webhook url]/deleteWebhook, but still same issue.
Please help
Every time I see a great n8n agent workflow it's buried in a forum post that disappears.
I built something and haven’t had any user uploading n8n templates so would appreciate if anyone would like to check and upload their open source work
agentshive.net, please provide your feedback and
Drop your best n8n agent workflow below — I'll add it as a featured template.
Hey everyone, I'm at the end of my rope with N8N. I’ve spent +40 hours trying to build a relatively simple PR workflow that takes 1) a Telegram message, 2) Sends it to an AI brain to analyze a prospect, 3) Then drafts custom pitch emails in my voice for books or podcast appearances.
I went the route of building this from scratch as opposed to copying someone else's template. As a veteran open source web dev, I thought I could probably learn N8N and build a functioning workflow in 10 hours. Now I'm thinking if I had just done PR stuff for 44 hours, I'd have a hell of a lot more to show for it!
I’m hosting n8n on Hostinger, and while I generally like them as a host, I’ve had nothing but endless, frustrating technical issues, from webhooks failing to my container unmounting entirely; randomly, one day they just deleted the workflow I'd been working on. (I could apparently jump through some steps to restore it, but I'm taking it as my sign to move on).
I've heard about "vibe coding," and THIS was the opposite of that. This was a flashback to my 2010 web dev days; squinting furiously at my screen, trying to find the errant syntax. My copilot in the development was Google Gemini; was this a major mistake? Should I have worked with Claude?
Are the other agentic tools like these as finicky? I had considered Open Claw or Hermes for my AI PR agent before settling on N8N. Somehow, I thought AI workflows would be "smarter."
My wife volunteered to do my PR; so basically, I can just take the workflow and templates I've built, give them to her, and she'll be the one getting my "trigger messages." There's no way she'll be a worse PR agent than what I built.
I might be convinced to stick with it if others here can reassure me that an N8N project doesn't entail a ton of ongoing maintenance. If I knew I was just a few more hours away from this thing working reliably with little to no ongoing maintenance, I might stick with it.
OK, ok, ok I'm kind of just venting here. So let's wrap up this ramble with a question that might provide value to everyone...
Do N8N workflows of average complexity work reliably once set up correctly?
Or do most N8N workflows have little things breaking all the time, randomly?
Is a working workflow set-and-forget, or will it take hours of upkeep a month?
I’m just about ready to fire the AI and hire the wife!
I find make the easiest => zapier=> n8n. Anyone can help with things n8n can which cannot. It’ll help choose the platform for future complex scenarios.
Hello lovely people here.
I'm stuck for few days with research of optimal exist solution or give up n8n automation for mine case for long context LLM chat like output from n8n for my automation purposes.
I am running a self-hosted stack. n8n plus OpenRouter plus SearXNG plus Jina/Crawl4AI plus Postgres. Goal is a research pipeline that gives chat-like output similar to Perplexity or a deep research mode.
Plan, search, fetch, synthesize with citations.
Current setup works but it is 10 plus nodes and multiple round trips to Postgres between steps. Every extra node is another place for a regression. I am not a developer. I need something stable that I can plug into any workflow without babysitting it.
I keep seeing Dify, LangGraph and Onyx recommended for this exact use case. Before I rebuild this from scratch I want real feedback from people who tried more than one of these.
Questions.
Does Dify or LangGraph actually hold long context and state across a multi step research loop better than n8n, or is it the same amount of complexity just hidden behind a different UI.
Has anyone moved a research automation from n8n to one of these and seen fewer regressions.
For someone without a dev background, which of these is realistically the fastest to self host and get stable, not just fastest to demo.
Not looking for theory, looking for what actually held up in production for you.
Thank you for any advice and response.
How to manage shared inboxes like sales@ career@ with n8n ? Auto reply, triage ?
I kept falling off Instagram because the grind isn't posting, it's the daily what-do-I-post-plus-make-the-graphic-plus-write-the-caption. So I moved that loop into n8n. Two workflows.
First one writes the content. A Basic LLM Chain node generates post drafts - hook, caption, hashtags, carousel slide text - into a Google Sheet marked ready-to-review. I fix what's clumsy and flip the good ones to approved. Nothing posts without approval.
Second one posts. On a schedule it grabs the top approved row, a rule picks one of a few branded HTML/CSS templates, a Code node fills it with the row's text, HTMLCSStoImage renders it to a PNG, and it goes up via the Instagram Graph API - single or carousel. Then it marks the row posted so nothing double-fires. Free tiers, no Canva.
Gotchas:
Not set-and-forget. AI drafts, I approve, it handles the design and posting. Fine by me.
Workflows (gist): https://gist.github.com/abhishek-geek/4d5e36e11641a1b428eb7ddae3044d5c
Full walkthrough: https://youtu.be/C_8Bl1qACis
Share me your Saas. I’ll try everyone
Put it in below format
Link - Tag Line
https://www.hyperdocs.io/ - FREE AI Documentation Software
I’ll share Free Product Docs Tool for the needed ones 😀
I don't know about you guys, but trying to handle complex API rate limits (like 429 Too Many Requests) purely using n8n visual nodes gets messy really fast.
Whenever I try to use the built-in "Retry on Fail" settings paired with Loop and Wait nodes, the canvas ends up looking like a complete nightmare. Plus, keeping a workflow "Waiting" for 5 minutes while it retries an API eats up server RAM if I have a hundred executions running at once.
Recently I just stopped forcing n8n to handle heavy logic loops. Instead of building 15 nodes to catch an error, sleep the system, and try again, I offloaded the actual API call logic into a lightweight Python script running locally.
Here is what the architecture looks like now:
It saves so much memory on my local Docker instance and keeps the visual workflow down to like 4 nodes instead of 20.
A failure mode that does not get talked about enough in n8n: the execution shows success, so everyone assumes it worked, but green only means the run finished without throwing. It does not mean the thing you cared about actually happened. The ones that burn people are the quiet ones. A scheduled flow that stops firing but still shows Active, no error anywhere. Or a token that expires and comes back 200 with an empty list, so the flow maps nothing forward and quietly writes blanks. Neither hits the Error Trigger, because nothing errored.
The cheapest thing that helps, no tool needed: for the flows a client depends on, add a check at the very end that the real outcome exists, the row actually landed or the email actually went, and have it shout if that comes back empty. And separately account for the run that never started, since a missing execution leaves nothing to alert on. What does everyone else do here, an error workflow plus checks, an outside pinger, or something else?
Hey r/n8n, I’m Hiyansh. I’m 10 years old and have been building AI/web stuff for a year now.
Wanted to share a flow I built. It takes Facebook Lead Ad submissions, runs them through GPT for qualification and scoring, pushes qualified leads into HubSpot, sends a personalised outreach email, and auto-follows up if there’s no reply (24h then 48h).
There’s a second branch as well: when a meeting is booked, it automatically adds to my calendar, and GPT generates a prep brief before the call.
Screenshot of the attached flow. Happy to answer any questions about the node setup, the GPT prompts for qualification, or the reminder logic if anyone is curious.
So as of lately (as you probably experienced already), reddit shut down API access for 99% of us who don't meet their requirements and can't register an app on their platform. They also made it difficult to programmatically access their old unauthenticated json endpoints.
Now I've been running a simple workflow for a long time, and all it did was fetch latest (<24h) posts from my 5-6 favorite subs once a day in the morning, get the most upvoted ones, feed them into Google Gemini, let it create a nice little TLDR / Top 10-style recap for the most interesting/groundbreaking ones, and mail it over to me so I could read it while sipping my morning coffee.
Now that my workflow didn't work anymore, I was a bit annoyed and my coffee wasn't as pleasant anymore. So today I managed to restore it, and I'm here to (briefly) share the steps, in case anyone wants to do the same.
First of all, the problem is they block you from accessing the json endpoints (if you're unauthenticated), unless you supply appropriate headers, user-agent and cookies. The HTTP request node by itself can't do it properly, for that you need to "fake" a first visit to Reddit, get the necessary tokens/cookies populated, and only then you can access the old unauthenticated json endpoints. So I used a mix of Browserless and Puppeteer API directly on the n8n host to work around this requirement.
>Note: this only applies to self-hosted instances - In my case I run it with Docker, but the same would work even without it.
edit your compose.yml file to add the browserless service:
services:
n8n:
image: docker.n8n.io/n8nio/n8n
# (your regular n8n config)
browserless:
image: browserless/chrome:latest
ports:
- "3000:3000"
environment:
- MAX_CONCURRENT_SESSIONS=5
and restart your n8n stack.
Add the following workflow to your n8n instance: RedditScraper.json
In your own workflows, invoke the RedditScraper subworkflow by adding an Execute Sub-Workflow node. Set it up so that it passes a single parameter called targetURL. This will be the full Reddit URL that you want to scrape (e.g. https://www.reddit.com/r/n8n/), plain and simple.
Output will be in JSON. If you used n8n Reddit nodes previously, the output is usable in the same way - everything is in the `data` object.
If you have a faster/better way to do this, I'm all ears!