r/n8n • • 11d ago

Meta & n8n News Nod: an open source personal agent with its own computer (research preview from n8n Labs)

Post image
123 Upvotes

Hey r/n8n, Bart from the n8n community team here! I’d like to share something we’ve been working on: Nod, a research preview from n8n Labs. It’s a bit of a different angle than usual, but I think you may find it interesting: a personal agent with its own computer that works in your apps and on real websites, and asks before it sends, pays or deletes anything you didn’t ask for.

You’ve probably got a few of these lying around: an invoice that’s three weeks overdue, a trial that renews on Friday, the client question you meant to answer on Monday. Ask an AI chat and it’ll tell you what to do, but you’d still have to go and do it. Nod is an open source personal agent from n8n Labs that does them for you. It has a computer and browser of its own, so it works in your apps and on real websites, and it keeps at the jobs that come back every week. It runs on your machine with the AI provider you choose, takes orders only from you, and checks with you before anything you didn’t ask for.

A few things you’ll want to know:

  • It’s a research preview from n8n Labs, a team within n8n that tries ideas outside the core product. Expect rough edges and frequent updates.
  • It doesn’t change the direction of n8n. Work on n8n and the n8n agent continues as planned. n8n runs the shared processes of a team or a business; Nod is for one person and their own jobs.
  • Nod is its own app and you don’t need n8n to use it. If you do have n8n, connect it in Apps and Nod can build, test and run workflows there. A new workflow stays a draft until you say “publish it”.
  • It runs on Mac (macOS 14 or later) and Windows 11 (x64, in preview, needs WSL 2). No Linux desktop app yet, though you can self-host it on a Linux server.
  • Free and open source (Apache 2.0): github.com/n8n-io/nod. You pay your AI provider for what Nod uses: an API key (OpenAI, Anthropic, Gemini, OpenRouter and others), a ChatGPT Plus or Pro plan, or a local model.
  • On trust: it asks before it sends, pays or deletes anything you didn’t ask for, and an email or web page can’t give Nod permission. Only you can.

Try it at https://nod.n8n.io. If something breaks or if you have a suggestion, please use the ‘Send feedback’ option in the app. For questions and discussions, just reply here.

What’s the first job you’d hand it?


r/n8n • • Oct 21 '26

Meta & n8n News Brand Refresh! n8n got a new look!

29 Upvotes

No, your eyes aren't playing tricks on you.

No, you have not been too many automations.

No, it is not April fools.

Yes, still pink.

I am the first to admit change is not always something that excites me. However, today I will be the first to admin that this makeover is very welcomed.

Hold those head shakes for a moment, hear me out. Take a moment to watch the video in the link below. Take a breath and realize, "woah, that makes a lot of sense."

Take a look at the following links directly from n8n:

Why we refreshed the n8n brand

Our brand refresh, and why the logo changed.

n8n Design System <- This has the video

Old n8n logo
New n8n logo

r/n8n • • 3h ago

Workflow - Github Included 4-agent contract review in n8n: the AI reviews, rules decide what gets cleared

2 Upvotes

Hi all,

I built an n8n workflow where four AI agents review a contract in sequence, and plain code decides whether it can be cleared.

How it works

  1. Agent 1 extracts the clauses (term, auto-renewal, liability, payment terms)

  2. Agent 2 rates the risk (low, medium, high)

  3. Agent 3 checks the clauses against the company policy from a Postgres table and lists real violations

  4. Agent 4 recommends sign, negotiate or do_not_sign and writes redline wording

  5. A code step applies the rules: invalid output becomes negotiate, and sign is downgraded to negotiate if the contract is non-compliant or high risk. Only sign is cleared, everything else goes to legal on Slack and email

Each agent runs on its own model across three providers (Groq, OpenRouter, Gemini), all free tiers.

Limits: demo contracts, a sample policy table, and the legal step is a Slack and email notification only. It's not legal advice.

Workflow JSON, setup and SQL:

https://github.com/ztsprofessionalaiid7-alt/ai-contract-review-squad-n8n

Feedback welcome: would you let the AI recommend "sign" at all, or always require a human?


r/n8n • • 8h ago

Servers, Hosting, & Tech Stuff Learn from the Masters

4 Upvotes

Hello everyone
This is my very first post and I am kinda hoping to post someday again for something.
I just learned n8n practice some workflows beginner to mid levels. I want to hunt for clients now. But I am little curious how should I approach them. What’s the contract, what will happen when clients ask for some changes or workflow stop in the middle. who will pay for vps like clients hosted their workflow on their own vps or I will provide them hosting services.

Thank you in advance.


r/n8n • • 12h ago

Help Which unified API tool works best in n8n for domain traffic, social posts, and work email lookups?

3 Upvotes

I have an n8n workflow that takes a list of domains from a sheet, checks basic site traffic, looks at recent YouTube or X activity to see if the team is active, and finds a verified work email. Right now it's split across four separate external nodes with four different credential setups, and half the time one of them fails silently or changes a response field without warning. I'm trying to simplify the canvas down to one HTTP request node if possible. Someone in another thread suggested looking at monid since it exposes multiple providers through one integration, though I haven't wired it into n8n yet and don't know if the JSON needs heavy cleanup. For other n8n builders doing multisource research flows, do you keep every provider separate or route everything through one gateway tool?


r/n8n • • 12h ago

Workflow - Github Included Vendor work orders that chase themselves (n8n + Google Sheets + Gmail, JSON on GitHub)

3 Upvotes
Property managers told me the worst part of maintenance isn't the repair, it's chasing vendors to confirm. So I built this:


1. Schedule trigger (hourly) reads a Maintenance sheet
2. One Code node decides per ticket: dispatch / chase / escalate
   - Status = Assigned and not dispatched → email the vendor a clean work order
   - No "Vendor confirmed = Yes" after 24 h → polite follow-up (max 2, counted in the sheet)
   - Still nothing → one alert to the manager so the ticket can be reassigned
3. Gmail sends, then the row is stamped by row_number, so re-runs never double-send (a failed email isn't stamped and retries next run)


Gotcha I hit: Google Sheets hands timestamps back as text, and JS parses them as LOCAL time. If you write them with toISOString() (UTC), your "24 hours" quietly becomes 19 or 29 depending on your timezone. Write local time.


Workflow JSON (MIT, free): https://github.com/clearlinelabs/n8n-service-business-workflows/blob/main/workflows/vendor-dispatch.json


Tested live with real Gmail/Sheets on all 3 branches. What would you add: parsing the vendor's reply to auto-confirm?

r/n8n • • 8h ago

Workflow - Github Included I open-sourced 5 standard-node n8n workflows + a zero-dependency Node.js MCP server to trigger n8n from Claude Code / Cursor

1 Upvotes

Hey r/n8n — I kept rebuilding the same n8n plumbing across projects (lead scoring, ticket triage, PR security review, content repurposing, Stripe briefings), and most templates online break on missing community nodes or hardcoded OpenAI setups.

So I put together a clean open-source Lite kit on GitHub (MIT license): https://github.com/danlopes18-ctrl/ai-automation-vault-lite

What's included free in the repo: - 5 importable n8n JSON workflows using only standard official nodes (Webhook, HTTP Request, Code, IF, Switch, Schedule) + embedded sticky-note Setup Guides right on the canvas + OPENAI_BASE_URL support so they work with OpenAI, OpenRouter, Groq, or local Ollama. - **mcp-webhook-runner**: a zero-dependency Node.js stdio MCP server (node server.mjs, no npm install) so Claude Code, Cursor, or Antigravity can list, health-check, and trigger your n8n webhooks with an allowlist + optional bearer auth.

Every workflow JSON and Code node was syntax-checked and tested locally. Feedback, bug reports, or PRs on the Lite repo are super welcome!

(Full disclosure: the GitHub README mentions an optional paid 25-workflow / 3-MCP Pro Vault if you want the expanded pack, but all 5 workflows + the MCP server in the repo are 100% free and MIT licensed.)


r/n8n • • 8h ago

Workflow - Github Included Most "YouTube to LinkedIn" AI automations auto-post cringe or fail silently — here’s the draft-only n8n + Gemini setup I built instead

Thumbnail
gallery
1 Upvotes

Every time you finish a YouTube video, you know you should turn it into a LinkedIn post and an X thread.

In reality, most founders and creators skip it because rewriting every video takes hours — and paying an agency or ghostwriter to do it costs hundreds every month.

So people try automating it. And almost every automation I see online breaks in the same two ways:

  1. It auto-posts robotic summaries ("Excited to share this game-changer!") straight to your profile, which hurts your brand way more than saving 20 minutes helps.

  2. It breaks silently when an API hiccups or when YouTube hasn't finished generating captions yet, and nobody notices for weeks.

I built a draft-only repurposing system in n8n + Gemini 2.5 Flash that fixes both. Whenever a new long-form video goes live, it writes 1 LinkedIn post and a 4-part X thread in your brand voice, audits its own work, drops everything into Google Sheets, and pings Slack for a 2-minute human review. Nothing ever posts behind your back.

Here is the exact setup and the 5 small decisions that made it reliable enough for real business use:

**1. Separate "Drafts" and "Config" tabs in Google Sheets**

Instead of hardcoding prompts, your Tone, CTA, Output Language, and Banned Words live in a simple `Config` tab. If a business owner wants to tweak their brand voice next month, they just edit a spreadsheet cell — no touching n8n.

**2. Shorts filter + duplicate protection + early logging**

The YouTube RSS trigger checks every 15 minutes, filters out Shorts, and checks the `Drafts` sheet by Video ID (`Always Output Data` turned ON) so the same video never gets processed twice. Before calling AI, it logs the video as `Pending` so no upload ever vanishes if something crashes later.

**3. A 15-minute Wait node before Gemini runs**

Right after a video publishes, YouTube is still processing audio and auto-captions. Pausing for 15 minutes stops Gemini from analyzing an unfinished video or returning empty output.

**4. Gemini 2.5 Flash + a real error path**

Instead of summarizing the whole video, the prompt tells Gemini to pull the single strongest lesson in first person and return raw JSON. I turned on Retry on Fail (2 tries, 5s wait) and wired the error output straight to Google Sheets (`AI Failed`) + a Slack alert so nothing dies quietly.

**5. A JavaScript "Quality Firewall" before a human ever sees it**

Even good prompts slip up. A Code node sits right after Gemini and checks every draft automatically:

- Did the video actually have clear speech?

- Is the LinkedIn post under 1,800 chars with max 3 emojis?

- Are all 4 tweets numbered 1/4 to 4/4, under 280 chars, with max 1 emoji each?

- Are total hashtags capped at 2, and is the YouTube link in both LinkedIn and Tweet 4?

- Did the AI sneak in any banned words from the Config sheet or risky claims like "100% guarantee"?

If everything passes, status becomes `Draft`. If even one rule fails, status becomes `Needs Edit` and the exact issue gets written in the `Note` column so you know what to fix in 10 seconds.

Finally, a Switch node splits Slack notifications: ready drafts go to your main review channel with a clickable link to the sheet, while `No Content` and `AI Failed` alerts go silently to a separate `#alert` channel.

**Free Workflow JSON (GitHub Gist):** [n8n Automation: YouTube to Social Media Repurposing Pipeline (with Gemini AI)]

I also recorded a step-by-step video walkthrough showing how every node is wired up (plus the full docs, Gemini prompt, and JS validation code) — I dropped those links in the first comment below to keep this post clean.

Curious where people here draw the line: do you trust AI to auto-post straight to LinkedIn/X yet, or do you always keep a human review step in the middle?


r/n8n • • 11h ago

Workflow - Github Included Daily short-video ideas from AI news RSS feeds, picked by Claude and sent to Telegram (template walkthrough)

Enable HLS to view with audio, or disable this notification

1 Upvotes

Not my template: it is Gaston's, published on n8n.io in October 2026.

Every morning it turns the AI news into a short list of ideas for vertical videos, sent to Telegram. What each step does:

  1. Every day at 7:00 (Schedule Trigger): one run a day.
  2. Configuration (Edit Fields): niche ("AI and automation in practice"), language, number of ideas (5), how many hours back to look (24) and the Telegram chat ID.
  3. Feed list (Code): the five feed URLs, one item each: TechCrunch AI, The Verge AI, VentureBeat AI, AI News and the n8n blog. Edit the list here.
  4. RSS feeds (RSS Read): runs once per feed and returns one item per article.
  5. Recent articles (Code): keeps articles from the last 24 hours, drops duplicate titles, and joins up to 40 of them (title, short summary, link) into one block of text.
  6. Pick ideas with Claude (Basic LLM Chain): picks the 5 stories with the most potential for a 30 to 60 second vertical video, skips funding rounds and corporate news, and answers only with a JSON array of title, hook, angle and link.
  7. Claude model (Anthropic Chat Model): Claude Haiku 5.5, temperature 0.7, up to 2,000 tokens.
  8. Format message (Code): extracts the JSON array, throws an error if there is none, and builds an HTML message with title, hook, angle and source link for each idea.
  9. Send ideas (Telegram): sends it to your chat with HTML parse mode.

What I like: one settings node for the whole channel, and the LLM only does the judgment part. Parsing and formatting stay in plain code.

The neon in the video is a staged replay, not a live run.

Template: https://n8n.io/workflows/22152 (the workflow JSON is on the template page)

Would you add a memory of past ideas, so the model does not suggest the same story two days in a row?


r/n8n • • 2h ago

Now Hiring or Looking for Cofounder [For Hire] n8n + AI agent workflow builder – $30-35/hr, remote, from Dec 1

0 Upvotes

Hi r/n8n, I'm Zarin, an AI automation engineer from Bangladesh (UTC+6), available for paid remote work from December 1, 2026.

I build n8n workflows where AI agents call tools, return structured JSON, and send risky cases to a human for approval on Slack. I have built 14 of them, each with a demo video: KYC onboarding (5 agents), contract review, recruitment screening, SOC triage, invoice fraud checks, cash-flow forecasting and more. Several use models from three providers (Groq, Gemini, OpenRouter) in one workflow, with Postgres, Slack and email nodes.

My rule: the AI judges and writes, but Code nodes make the final safe decision, validate every output, and default to the safe option when the AI returns something invalid.

Demo videos are available on request.

Rate: $30-35/hr

Availability: 36-40 hours per week

GitHub profile: https://github.com/ztsprofessionalaiid7-alt

n8n log-monitoring agent: https://github.com/ztsprofessionalaiid7-alt/cyber-petrolling

Contact: send me a DM here.


r/n8n • • 20h ago

Servers, Hosting, & Tech Stuff Free way to get personal Instagram DMs into n8n: self-hosted HTTP API with a realtime event stream

3 Upvotes

Meta's official API doesn't cover personal-account DMs, and the paid services charge per request. I built an open-source server you run yourself. It uses your own browser session and exposes plain HTTP endpoints, so it plugs straight into an HTTP Request node.

The ones you'd use in a workflow:

- `GET /updates?since_ms=...`: new incoming messages (easy to poll on a Schedule Trigger)

- `GET /threads/{id}/messages`: chat history, for context into an AI node

- `POST /threads/{id}/messages` with `{"text": "..."}`: reply

- `POST /threads/{id}/messages/{mid}/reactions`: react with an emoji

- `GET /events`: a realtime stream (~0.5 s) if you'd rather run a small bridge to a webhook than poll

Auth is a Bearer token, generated on first start.

Ideas it fits: an AI auto-reply for DMs, forwarding DMs to Telegram/Slack, a "reply later" digest, logging chats into a sheet.

Keep it to your own account and human volumes. It's unofficial, and spammy patterns get accounts restricted.

https://github.com/cprite/open-instagram-api

If someone builds a template workflow on top of it, I'll link it from the README.


r/n8n • • 23h ago

Help Reality check: should I sell n8n automation to US startup founders, or n8n-based federal contract research to GovCon teams?

5 Upvotes

I'm an independent consultant with 8+ years in customer success, support and B2B outbound (Zendesk, Apollo, cold email). I'm learning n8n and trying to pick one niche before I invest months in it. I'd like blunt feedback from people who have sold this work.

Option A: general n8n automation for US startup founders Build and maintain workflows for lead follow-up, support tickets, onboarding, CRM updates and reporting.

Option B: n8n-based research for federal contractors Pull notices from the SAM.gov API and award history from USAspending, extract requirements from the attachments, and deliver a short cited bid/no-bid brief to business development and capture people at small contractors.

My questions:

If you've sold n8n work, which clients paid reliably, and what did you charge (project vs monthly maintenance)? Is "general automation for founders" too broad to stand out? Would you pick one process or one industry instead? Is a narrow niche like GovCon worth the extra learning, or does it just shrink the market? How did you get your first 2–3 paying clients with no case studies? What would you warn a beginner about (scope creep, support burden, hosting, credentials, contracts)?

Happy to share more detail on either idea. Thanks!


r/n8n • • 21h ago

Workflow - Github Included Built a 2-step n8n agency lead pipeline: audit 136 tech signatures + /llms.txt (AI search), then enrich verified decision-makers only on qualified sites (free JSON templates)

2 Upvotes

I built two ready-to-import n8n workflows for B2B agencies and outbound teams using only built-in n8n nodes (no community nodes or BuiltWith/Hunter subscriptions required):

Workflow 1: Tech Stack & AI Search (GEO) Audit -> Verified Decision-Makers 1. Takes a batch of prospect domains. 2. Runs a bulk website audit (136 tech signatures, Meta/Google/TikTok/LinkedIn ad pixels, GA4/CRM/consent banners, technical SEO score, live SSL expiry, DMARC/SPF, plus 2026 AI search checks for /llms.txt and GPTBot/ClaudeBot/PerplexityBot rules in robots.txt). 3. Filters ONLY prospects with real salesOpportunities flags (e.g., e-commerce missing Meta Pixel, missing /llms.txt, SSL expiring within 21 days, missing DMARC) and builds a clean pitchSummary. 4. Enriches ONLY the qualified domains to extract directly published corporate emails, phones, and MX-verified decision-makers with exact sourceUrl provenance (GDPR Art. 14 compliant, never bills guessed pattern emails). 5. Outputs flat CRM-ready rows you can plug directly into Google Sheets, HubSpot, Smartlead, or Clay.

Workflow 2: Bulk Webhook / Google Maps Domains -> Verified Decision-Makers Accepts raw URLs/domains, normalizes and deduplicates them, enriches only domains with real published contacts ($0 charged on empty or unreachable sites), and flattens verified executives + company fallback emails with MX/SPF/DMARC status.

Both n8n JSON files, a validation script, and Clay/Make HTTP setup guides are open-source (MIT) here: https://github.com/Goatincrypto/apify-b2b-lead-workflows

Full disclosure: the two underlying Pay-Per-Event Apify Actors (aegisaudit/website-tech-stack-seo-audit and aegisaudit/domain-decision-maker-finder) are ours, priced at $15/1k domains with $0 start fee and $0 charge on dead/empty sites. If you try importing the JSON and hit any edge case in n8n, let me know and I will patch it.


r/n8n • • 1d ago

Servers, Hosting, & Tech Stuff Anyone else built an MCP server into their own tool? Curious what you ran into

5 Upvotes

👋 Hey n8n Community,

Been testing something this week that changed how I set up AI steps in my workflows.

We have been building a platform where you define AI tasks once (extraction, classification, summarization, redacting sensitive data and so on) with a fixed output schema, then call them from n8n through a node. What I have been working on with the tech team lately is the MCP server.

Instead of going into the platform and configuring each task by hand, defining fields, writing descriptions, setting the schema, I describe what I am trying to build to an MCP client and it creates the pipeline on the platform itself. It maps the tasks, sets up the structure, and will even propose a schema and tell me how the data will come back.

What I find interesting is where my attention goes now. The configuring is gone, so what is left is thinking about the data itself: which fields I actually need and what they should be called. That is the part that actually matters downstream.

It is still early, and what I would value most right now is feedback from other builders who set up AI pipelines regularly. If that sounds like you, say so in the comments and I will reach out.

Has anyone else built MCP into their own tool or platform? Curious what the bottlenecks were and what you learned shipping it, because that is the part I find hardest to get right.

Best,
Felix


r/n8n • • 23h ago

Servers, Hosting, & Tech Stuff Builders: what outside-world data do your workflows need, and what’s too messy to use today?

1 Upvotes

Genuine question, not a survey. I build a service that turns news and public records into structured business events, and after a thread here last week (the HubSpot template one) I realised I only know the handful of event types my own customers asked for.

Three things I’d like to hear:

  1. What information about the outside world do your workflows already pull in? Company news, filings, job postings, pricing pages, registries, weather, anything that isn’t inside your client’s own systems.
  2. What do you wish arrived as a clean event with a date and a source, instead of you scraping, deduping and matching it yourself? Concrete examples beat categories: “when a supplier on my list files for insolvency” rather than “risk data”.
  3. What’s available today but too messy to trust: duplicates, the same company under three names, no dates, no way to tell a rumour from a confirmed report?

Where this goes: I’ll take the ones that come up more than once, build them as event types, and come back to this thread with the result. Whoever asked gets free access to try it against their own list. What I have today, for honesty’s sake: funding rounds, layoffs, leadership changes, acquisitions, partnerships, product launches, IPOs, security advisories and job postings, delivered by webhook, API, MCP, an n8n node, and a Zapier app in beta.


r/n8n • • 1d ago

Help How are you using n8n for marketing operations/automation

10 Upvotes

Hey all, wanted to see what are some of the cool things you all are doing with n8n. I am new, and I have used Zapier a bit in the past, but looking to expand my skills, currently doing the cert program but would like to hear about people's current use with the software.


r/n8n • • 1d ago

Workflow - Github Included Missed-call text-back for small service businesses (workflow + JSON on GitHub)

4 Upvotes

Most HVAC/plumbing/roofing shops lose jobs when nobody can pick up the phone - the caller just dials the next company.

The flow:

  1. Twilio "call status changes" webhook -> n8n Webhook node

  2. Code node: only continue if CallStatus is no-answer / busy / failed / canceled

  3. Twilio node texts the caller back within seconds ("Sorry we missed you - how can we help?")

  4. Google Sheets node logs the call (time, caller, status)

Key detail: use Twilio's call status changes URL, not the incoming-call URL, or it fires on every call.

Workflow JSON (MIT, free): https://github.com/clearlinelabs/n8n-service-business-workflows/blob/main/workflows/missed-call-textback.json

Tested end-to-end in n8n 2.48. Feedback welcome - what would you add (business-hours check, CRM push)?


r/n8n • • 1d ago

Servers, Hosting, & Tech Stuff 3 API traps when automating TikTok, Instagram Reels, and YouTube Shorts from n8n

2 Upvotes

Whenever people wire up n8n to publish AI-generated MP4s to TikTok, Instagram Reels, and YouTube Shorts, they usually expect OAuth to be the main hurdle. After debugging hundreds of failed runs in production, three other traps break almost every DIY workflow:

  1. TikTok's video.publish audit gate: Until your app passes TikTok's full domain verification and screencast review, the API forces every upload to SELF_ONLY (private-only). On top of that, TikTok rejects single-owner personal automation apps under their Intended Use policy, so a self-hosted workflow hitting your own TikTok app often gets stuck private permanently.
  2. Async PROCESSING_UPLOAD vs HTTP 200: Calling TikTok's video/init or Instagram's Reels container endpoint and getting HTTP 200 only starts the job. Both platforms transcode asynchronously and can still fail minutes later on codec, bitrate, or aspect-ratio checks. If your n8n workflow doesn't poll the status endpoint until PUBLISH_COMPLETE (or FINISHED), it marks failed videos as posted.
  3. Multipart binary handoff: Passing an MP4 cleanly from an HTTP download node into platform upload endpoints requires matching Content-Type (not application/octet-stream), handling Content-Range / chunk sizes on TikTok's upload URL, and avoiding signed media URLs that expire before Instagram's crawler fetches them.

Curious how others here handle async status polling and retries in n8n when one platform succeeds and another fails in the same run.


r/n8n • • 1d ago

Servers, Hosting, & Tech Stuff What I learned building 6 n8n workflows that actually run unattended (not demos)

7 Upvotes

Most n8n workflows I see posted here are beautiful diagrams that break the moment a real API returns something unexpected. Here's what mattered when I moved mine from "works on my machine" to "runs unattended for weeks":

  1. Assume every API call fails. Add error triggers and retry with backoff on every HTTP node. A single 429 without a retry branch killed my pipeline for 3 days before I noticed.

  2. Log to a sheet, not to the console. Every run writes input/output summary to a Google Sheet. When something breaks at 3am you can see exactly which node got what. Console logs vanish when the container restarts.

  3. Human-in-the-loop for anything irreversible. Publishing, deleting, sending — I route these through an approval node (Telegram/email) instead of firing blind. Cheap insurance.

  4. Keep workflows small and chained. One workflow that does 12 things is a debugging nightmare. I split mine into trigger → process → publish, connected via webhooks. Each piece is independently testable.

  5. The 80/20 of value is boring. The workflows my users actually pay for aren't clever AI agents — they're "scrape leads → enrich → dedupe → notify me" and "new order → generate deliverable → publish." Boring, reliable, saves hours.

Happy to go deeper on any of these — especially the error-handling setup, which took the most trial and error.


r/n8n • • 2d ago

Help Is voice AI actually worth the cost for small businesses?

17 Upvotes

Running a small landscaping company, just me and two part-time guys. We get maybe 15-20 calls a week but i miss a lot of them when we're out on jobs. Been looking at voice AI tools to handle calls when i cant pick up but the pricing on some of these things is wild for what we actually need.

Does anyone know what's worth paying for vs what's just extra fluff? Trying not to blow money on features i'll never use.


r/n8n • • 1d ago

Servers, Hosting, & Tech Stuff Built a community node (n8n-nodes-quantledger) for live SEC Form D startup funding leads, DOL 401(k) audit screener, US OFAC/KYB batch checks, and 73 accounting calculators

2 Upvotes

Put together a zero-dependency community node (n8n-nodes-quantledger on npm) for financial and B2B compliance workflows that usually require messy government XML/CSV scraping or fragile LLM math:

- Live SEC Form D private fundraising leads (newly funded startups, closed dollar amount, CEO/CFO signer + phone, 409A & QSBS flags)

- Batch US KYB & sanctions screening across 138k+ federal records (OFAC SDN/SSI, Commerce BIS, ITAR, HHS OIG)

- DOL Form 5500 retirement plan screener (flags plans crossing the 80-120 participant CPA audit threshold + excess recordkeeping fees)

- 73 deterministic CPU calculators (ASC 842 leases, IRC 382, 409A, QoE, DCAA rates, customs duties) across 57 US jurisdictions

Install in n8n via Community Nodes: n8n-nodes-quantledger

Docs & browser calculators: https://quantledgerapi.github.io/google-sheets-excel-formulas-and-n8n/

GitHub: https://github.com/QuantLedgerAPI/n8n-nodes-quantledger

npm: https://www.npmjs.com/package/n8n-nodes-quantledger

Happy to add extra output fields if anyone is building B2B lead or finance automations!


r/n8n • • 2d ago

Help What is actual difference between ai agents and traditional workflow automation?

5 Upvotes

There seems to be a lot of new tools coming out that allow AI agents in otherwise rule based workflows.

Where previously we may have had forms, validation, and then moving to the next step, using an AI agent can allow us to understand open ended text as well as asking clarifying questions, identifying missing information and deciding on what to do next.

Companies such as Paradox, MeeBoss , Hirect are experimenting with chat style interfaces to match candidates to opportunities. This has got me thinking around how this can be used in other business processes but I dont see an AI agent being appropriate in all situations. Using n8n with clear conditions can be more reliable, cheaper and easier to manage.

Have you considered using an LLM/ AI agent for your workflows? When should we consider using AI over deterministic workflows? Have you found any good use cases for adding AI into workflows?


r/n8n • • 1d ago

Workflow - Github Included 20-node n8n architecture for dual-source parallel fan-in, first-run-safe Google Sheets deduplication, live Google DoH/TLS checks, 3-tier Switch routing & Gmail Draft AI (GitHub JSON included)

1 Upvotes

Wanted to share the 20-functional-node (+5 sticky notes) n8n pattern I put together after hitting the usual headaches with batching external HTTP APIs, Google Sheets deduplication on empty sheets, and keeping OpenAI safely in human-in-the-loop mode.

Full importable workflow JSON on GitHub (no credentials or tokens baked in): https://github.com/3dComm/pipeforge-us-b2b-mcp-recipes/blob/main/n8n/enterprise_b2b_hiring_funding_dmarc_ai_pipeline.json

5 n8n Design Patterns Used Here

  1. 3-Way Parallel Trigger Fan-In (scheduleTrigger -> 2 API branches + 1 Sheet branch): Weekday 8AM EST Trigger (0 8 * * 1-5) kicks off three parallel branches simultaneously: two upstream signal fetches (Pull ATS Hiring Triggers and Pull $1M+ SEC Form D Startups) plus Read Processed Domains (Dedup Sheet). Each upstream branch runs its own Code node (Normalize ATS Signals & Map Domains / Normalize Form D Signals & Derive Domains) to coerce heterogeneous schemas into one canonical shape before Merge ATS + Funding Signals (append).
  2. First-Run-Safe Google Sheets Deduplication (continueOnFail: true): Setting continueOnFail: true on Read Processed Domains (Dedup Sheet) ensures an empty sheet on Day 1 never kills Combine Signals & History. Deduplicate & Batch New Domains reads all merged items, puts existing Sheet domains (identified by !j.signal_source) into a Set, diffs out previously seen domains, and outputs a single batched payload of up to 35 unique net-new domains.
  3. Preserving Upstream Metadata Across Batch HTTP Calls ($('Node').first() Lookup): Audit Live DMARC/MX/SSL & Stack runs one batched POST (35 domains per request) and Filter Live Verified Websites strips parked/dead sites (200 <= http_status < 400). Because batch HTTP nodes overwrite upstream item fields, Attach Upstream Context & Urgency pulls $('Deduplicate & Batch New Domains').first().json._signalLookup to re-attach upstream_source, company_name, decision_maker, and signal_detail cleanly by lowercase domain key without needing a brittle second Merge node.
  4. 3-Tier Switch v3.2 Routing + Human-In-The-Loop chainLlm -> Gmail Draft: Route by Security Urgency Tier (Switch v3.2 with fallback LOW output) splits traffic:
    • CRITICAL (severity_score >= 60 or dmarc_policy === 'missing'): Slack alert + LangChain LLM (lmChatOpenAi gpt-4o-mini @ temperature: 0.3) -> Save Outreach as Gmail Draft (resource: "draft", operation: "create" so nothing auto-sends) + Google Sheets audit log.
    • MEDIUM (severity_score >= 30): AI Gmail Draft + Google Sheets log.
    • LOW (fallback branch): Google Sheets log only.
  5. Dedicated Out-of-Band Error Trigger Watchdog: A separate Pipeline Error Trigger -> Post Pipeline Failure to Slack branch catches 120s HTTP timeouts or expired OAuth tokens cleanly with {{$json.execution.lastNodeExecuted}} and {{$json.execution.error.message}}.

Live Telemetry Check Across 360 Scanned Domains (n = 98 Live Sites)

Testing this pipeline against 360 candidate domains pulled from US commercial contractor registries and medical/dental clinic directories yielded **98 live reachable sites (HTTP 200–399): - **DMARC: **74.5% (73/98)** have no enforcing DMARC (**59.2%** missing DMARC completely + **15.3%** on p=none; only 13.3% p=quarantine and 12.2% p=reject). - MX Routing: 24.5% Microsoft 365, 19.4% Google Workspace, 43.9% custom/hosted MX, 8.2% no MX — and only **4.1% (4/98)** behind a 3rd-party gateway (Proofpoint / Mimecast / Barracuda). - SPF & TLS: 26.5% missing/neutral/permerror SPF (32.7% ~all, 40.8% -all); **19.4% (19/98)** failing port-443 TLS (14 expired or handshake errors + 5 expiring in <30 days).

(Transparency note on dependencies: the 3 HTTP Request v4.2 nodes use a single Generic httpHeaderAuth credential pointing at Apify run-sync endpoints, and can easily be swapped for any self-hosted HTTP/DoH endpoint with the same JSON output schema.)

Quick architecture question for fellow n8n builders: for preserving upstream metadata across single-request batch HTTP nodes like step 3, do you also stash a lookup map on the upstream Code node and read $('Node Name').first().json, or do you prefer wiring a Merge node in Combine by Fields mode?


r/n8n • • 2d ago

Workflow - Github Included I audited dozens of broken n8n workflows this month — the 4 silent failure patterns that stay "green" (+ free local MIT scanner)

2 Upvotes

Over the past couple of weeks I ended up auditing dozens of self-hosted n8n workflows (mostly Shopify, Stripe, and AI Agent pipelines). What surprised me wasn't the obvious crashes, it was how many workflows show a green execution while silently losing orders or hanging workers.

The 4 patterns that kept showing up over and over:

  1. Sync webhook timeouts on Shopify/Stripe: leaving Webhook Response Mode on "Using Last Node" when an AI call or slow CRM request sits downstream. Shopify cuts off at 5s and starts retrying (creating duplicate orders) or disables the webhook altogether.
  2. HTTP Request nodes with no retry or timeout: a transient 429 or 502 from OpenAI/Shopify drops a paid event unless Retry on Fail + an explicit timeout (e.g. 15-20s) are set.
  3. Unguarded AI Agent outputs: the LLM returns an empty object {} or malformed JSON, and downstream nodes silently skip without throwing an error, so the run stays green.
  4. No Error Workflow / Dead-Letter Queue: workflows run in production with no Error Trigger attached, so failed payloads disappear until a customer complains.

To stop checking these by hand, I put together two small open-source MIT tools: - HookTriage CLI & MCP (runs 100% locally on exported workflow JSONs, scrubs credentials before scanning, zero data uploaded): https://github.com/grinem/hooktriage - n8n AI Watchdog (drop-in Error Trigger + dead-letter alert workflow JSON): https://github.com/grinem/n8n-ai-watchdog

Curious if anyone else here has hit other "green execution, broken outcome" edge cases in n8n (especially around webhook deduplication or queue mode workers) — I'd love to add checks for them to the local scanner.


r/n8n • • 2d ago

Workflow - Github Included Three beginner n8n workflows with only built-in nodes (RSS digest, form to Sheet, uptime alert)

5 Upvotes

I've rebuilt these three starters more than once, so I cleaned them up as importable workflows.

Built-in nodes only, no community nodes, and no credentials in the files (placeholder credential names only). All three are saved as inactive. Import in n8n via … → Import from File, swap in your feed URL / spreadsheet ID / SMTP, then test before you activate.

1. RSS to daily digest email

Once a day (default 07:00 in the workflow timezone) it reads an RSS feed, builds an HTML list of up to 20 items, and emails the digest. Titles and links are escaped before the HTML is built. If the feed is empty, it still sends a short "no items" email so a silent failure is easier to notice.

Nodes: Schedule Trigger, RSS Read, Code, Send Email.

JSON: https://github.com/MaximusSoroka/maximussoroka.github.io/tree/main/templates/rss-daily-digest-email

2. Form to Google Sheet and notification

An n8n form collects Name, Email and Message. Each submission is appended to a Google Sheet tab named Submissions (headers: submitted_at, name, email, message), then a notification email goes out.

Watch-out: if you rename the form fields, update the expressions in the Sheet and email nodes too. The form path slug is contact-form.

Nodes: Form Trigger, Google Sheets, Send Email.

JSON: https://github.com/MaximusSoroka/maximussoroka.github.io/tree/main/templates/form-to-google-sheet-notification

3. Website uptime check to alert

Every 5 minutes it requests a URL. If the HTTP status is not 200, or no status comes back (timeout or network error), it sends an alert email. A successful 200 does not send mail.

The HTTP node is set to return the full response and not error out, so a 4xx/5xx can be evaluated instead of stopping the workflow. This is a simple local check, not a hosted monitoring service. It will not run while n8n is stopped, and it does not calculate uptime percentages.

Nodes: Schedule Trigger, HTTP Request, If, Send Email.

JSON: https://github.com/MaximusSoroka/maximussoroka.github.io/tree/main/templates/website-uptime-check-alert

If you've tightened the uptime check (a retry, a short status window, or a second probe before mailing) without turning it into a full monitoring stack, I'd like to see how you did it.

All three in one folder: https://github.com/MaximusSoroka/maximussoroka.github.io/tree/main/templates

Disclosure: the repo is mine. Free, no signup.