r/n8n • • 8d ago

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

Post image
124 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 • • 29d ago

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 • • 5h ago

Help 🙏 Looking for Suggestion - From the Expert/OGs of the fields.

3 Upvotes

Fellow Redditors,

How is everyone using multiple coding agents on the same project without stale context or conflicting changes?

I use the Codex app, OpenCode CLI and Antigravity IDE. Would appreciate a better setup if exists or is preferred.

Ideally, I would like to assign five separate issues and have all agents work on them in parallel without overwriting each other’s changes or making incompatible decisions.

Two things I’m struggling with:

  • Keeping context current: How do you automatically update AGENTS.md or other project notes after meaningful changes? Are you using hooks, memory tools or another approach?
  • Coordinating parallel work: Do you use separate Git worktrees, a coordinator agent, task ownership or something else? How to work with multiple agents at the same time

I’m especially interested in setups that work across different tools and models.

Would love to hear your actual workflow, including what went wrong and what you simplified.


r/n8n • • 38m ago

Workflow - Github Included Evaluating LLM outputs with independent judges: an LLM-as-Judge pipeline in n8n

1 Upvotes

Hi r/n8n,

I built an evaluation pipeline in n8n where one model's answers are scored by two independent judges from different providers, and I'd like feedback on the design.

Problem

Using an LLM to grade another LLM is convenient, but a judge that shares a model family with the candidate tends to favour its own answers, and a single judge gives you no sense of how much to trust its scores.

Design

  1. Test set: 5 questions (facts, math, tech, reasoning), each with a reference answer and a human score
  2. Candidate: Groq (gpt-oss-20b and gpt-oss-120b, tested in separate runs)
  3. Judge A: Gemini 3.5 Flash Lite. Judge B: Nemotron 3.5 Lightning via OpenRouter (free). Both score 1 to 5 against the question and the reference, and neither is the candidate model
  4. Scoring in code: judge average, absolute error against the human score, pass (average of 4 or more), agreement with the human (within 1 point) and judge disagreement (2 points or more)
  5. Reporting: run-level metrics go to Slack and email, and items and runs are stored in Postgres (Supabase)

Why it is built this way

Cross-provider judges remove self-preference. Judge disagreement is tracked as its own metric, so you can see where the scores are unreliable. Agreement with human labels is the check on whether the judges can be trusted at all.

Limitations

- Five questions is a demo. The numbers are not statistically meaningful, and a real evaluation needs a larger labeled set

- The human scores in the test set are starter labels and need to be replaced with your own

- An answer a judge cannot return as valid JSON is scored as 1, which can understate the candidate

Repository (workflow JSON, setup steps, table SQL):

https://github.com/ztsprofessionalaiid7-alt/llm-judge-eval-pipeline-n8n

Questions for the community

- Would you add a third judge, or a tie-break rule when the two disagree?

- How large a labeled set do you use before trusting judge-human agreement?


r/n8n • • 1h ago

Workflow - Github Included I built an n8n agent for forgotten trials, unused subscriptions, and a drained account before payday (JSON on GitHub)

Post image
1 Upvotes

Trial you forgot. An account drained a week before the month ends. A subscription you never use. Guilty as charged on the first one. So I built two n8n agents that share one Telegram chat, and my family uses it every day.

What it does

  • Trials and subscriptions: from 7 days before renewal, it sends a message every second day until you reply "keep". Reply "cancel," and it searches the web for the cancel steps and saves the link.
  • Expenses: send text ("coffee 4 € revolut"), a voice note, or a receipt photo. It asks only for what is missing: the card, who paid, and the category.
  • Budget: each expense gets a card with the category bar. At 80% you get a warning. At 100%, it asks whether to raise the budget for this month, for the rest of this month, or leave it.
  • Two people, one bot: "Sam paid" moves the expense to the other person.

How it is built

  • WF1 router: a tag (#budget, #subscriptions) or a reply to the bot is matched by code, with no model call. A message without a tag goes to a classifier that also sees the last agent reply (if under 6 hours old). When it can't tell, it asks.
  • WF2 schedules: daily check-in, weekly summary, renewal check, month-end review, and a month setup with no AI.
  • Data: 4 Notion tables, Postgres for chat memory, and an n8n Data Table as an action log, so "try again" can't create a duplicate expense.
  • Numbers come from Code nodes. The model only reads them.
  • Model: Venice through an OpenAI-type credential. Any OpenAI-compatible API works.
  • Currency: it runs in PLN because I live in Poland, with € converted at the daily rate. You can change it in the Notion tables and the workflows.

JSON files and README (table columns, credentials, publish order): https://github.com/thalderg/n8n/tree/main/workflows/budget-coach

Full step-by-step guide (free link): https://medium.com/@giopag81/how-to-never-forget-what-you-spend-with-n8n-ed88174291ce?sk=a1708399e9bbba18da25ae7b6df44d23

Ask me anything about the router or the Notion setup. If you'd rather not build it yourself, send me a DM.


r/n8n • • 13h ago

Workflow - Github Included Made an invoice checker in n8n where Claude only reads the document and plain JS does all the checking (repo inside)

2 Upvotes

I wanted to try something in n8n that actually touches money, so I built a workflow that reads invoices and receipts and checks them before anything gets paid. You upload PDFs, scans or phone photos, it pulls out the supplier, dates, line items and totals, and then it checks if the math adds up, if the same invoice already came in before, and if the prices match the quote you agreed on. If something's off it gets flagged with a note saying what to look at.

The upload goes into a Webhook node and a Code node splits it into one item per file with the binary as base64. Then an HTTP Request node sends each file to the Claude API, PDFs as a document block and photos as an image block, with a JSON schema so everything comes back structured, and every field also gets its own confidence level. After that it's just a Code node doing the checks in plain JS against the Data Tables: line math, subtotal plus tax against the total, duplicates, and unit prices against the quote. The pages are HTML built in Code nodes and sent back with Respond to Webhook, and the upload webhook only responds when the last node finishes, with a 303 redirect, so the browser just waits while it reads and then lands on the updated list.

What made the biggest difference was telling the model to report the numbers exactly as printed and never fix them. If you don't, it sometimes corrects a wrong total on its own, and then the one mistake you were trying to catch just disappears. The confidence per field turned out really useful too, because a blurry total on a phone photo becomes a "check this" flag instead of a wrong number.

One annoying thing I hit: Data Tables with "create if not exists" kept throwing a name conflict when one table name was part of another ("Paperwork" and "Paperwork files"), and it only went away once I renamed them so no name contains another. Honestly not sure if that's a bug or I'm missing something, so if anyone knows I'd like to hear it.

The video is 6 sample documents, a couple of PDFs, a crooked scan, phone photos and one invoice in German, and it took about 12 seconds for all of them.

Repo with the three workflows, the sample docs and setup steps: https://github.com/Mangel-bit/n8n-invoice-checker

If you have a better idea for the duplicate check I'm all ears, right now it's just same supplier plus same invoice number, or same total on the same date.


r/n8n • • 19h ago

Workflow - Github Included Flag possible duplicate supplier invoices in a Google Sheet before the pay run, with Slack (free, on GitHub)

2 Upvotes

I put together a workflow that reads a Google Sheet of supplier invoices every weekday at 08:00 and flags pairs that may be the same bill twice. New pairs go to a review tab in the same spreadsheet, and Slack gets one message listing them. It uses Google Sheets and Slack only, with no AI node. The workflow JSON, a README and the sheet headers are on GitHub: https://github.com/jessymariau/n8n-duplicate-invoice-flag

Three choices I made that you may find useful:

  1. The review tab is the memory. Each flagged pair gets a pair_key, built from both rows with the two halves sorted, so A-vs-B and B-vs-A are the same key. Next morning the workflow reads the tab and drops any pair already in it, so nobody is told about the same pair twice. There is no state to store anywhere else, and a person can delete a row to have a pair raised again. This is the whole Code node (Keep Only New Pairs):
const flagged = new Set($('Read Already Flagged').all().map(i => String((i.json || {}).pair_key || '')).filter(Boolean));
return $('Find Duplicates').all().filter(i => !flagged.has(i.json.pair_key));

The Read Already Flagged node has alwaysOutputData on, so an empty tab on the first run does not stop the chain.

  1. Names and numbers are tidied before anything is compared. Ltd, Limited, plc and punctuation are stripped from the supplier, and the invoice number loses its prefix and leading zeros, so INV-000123 meets 123. Without this, the same invoice resent in a slightly different format never matches. The Find Duplicates node does it with two small functions at the top, and the compare loop is a plain nested loop over rows.

  2. Three verdicts instead of one score: EXACT DUPLICATE (same number and amount), SAME NUMBER, DIFFERENT AMOUNT (a resend or a correction), and SAME AMOUNT, DIFFERENT NUMBER, which only counts when the two invoices are within a date window (45 days by default) and the amount is above zero, so credit notes do not trigger it. The label tells the person reading the Slack message what to look at first. The thresholds are in a Settings node: amountTolerance, dateWindowDays and the four column names.

The Slack message is built in its own Code node (Write One Summary), so one run gives one message however many pairs were found. It lists the first 15 and says how many more are in the sheet.

What it does not do: it does not block a payment, it only flags. It compares rows already in the sheet, so it does not read PDFs or emails. It compares every pair of rows, so a very large sheet will be slow. Two spellings of a supplier that tidy to different text count as different suppliers.

What I tested: nothing, in the sense of a run. It has not been run end to end, and it has not been connected to a real Google Sheet or Slack workspace. The only check on file is a read-through of the workflow file against its description. Try it on a copy of your sheet first and tell me what it gets wrong.


r/n8n • • 12h ago

Help If you’re NOT running an agency, keep scrolling

0 Upvotes

In business, there are visible things and invisible things.

The results you deliver are visible. The trust and confidence you build with your clients are not—and they can break easily.

Outside of n8n, what tools do you use to protect those invisible things like reliability, security, and speed to keep operations running smoothly and deliver a great client experience?


r/n8n • • 1d ago

Workflow - Github Included I built a security incident investigation agent in n8n that follows my playbooks instead of inventing steps

0 Upvotes

Hi all,

I built an n8n workflow where an AI Agent investigates a security incident report and writes the incident report, but its containment steps come from a playbook table in my database instead of its own imagination. Sharing it on GitHub for feedback.

The idea

When an incident comes in, the first hour is mostly the same: check the indicator, work out what kind of incident it is, find the procedure, write it up. That part is a good fit for an agent, as long as it follows the procedure the team already has.

How it works

  1. Mock incident reports arrive: a phishing email that three staff clicked, encoded PowerShell on a file server at 3 AM, and a storage bucket made public
  2. Playbooks are read from a Postgres playbooks table, and the best match is added to the case by keyword
  3. An AI Agent (Gemini) calls an ioc_check tool with the key indicator and writes the report as JSON: incident type, priority, likely cause, impact and containment steps, based on the playbook
  4. A code step validates the output. Priority P1 (active compromise or exposed data) becomes escalated, everything else is logged
  5. Escalated incidents go to a Slack war room channel, and every report is saved to Postgres

Why the playbook table

The agent follows your procedure and can't make up a containment step. Change a row in the table and the next report changes, no prompt editing.

Stack: n8n Cloud, Gemini, Slack, Supabase (Postgres). All free tiers.

Limits, to be clear about them

- The ioc_check tool and the incidents are mock data

- The priority comes from the model and is only validated in code (P1, P2 or P3, default P2). So whether something is escalated depends on the model's judgment, not on a hard rule. In my SOC triage repo I did the opposite, rules decide, and I'd like to bring that here

- It only investigates and writes a report, nothing is executed automatically

Workflow JSON, setup steps and table SQL:

https://github.com/ztsprofessionalaiid7-alt/incident-investigation-agent-n8n

Feedback welcome: which checks would you put in code to decide P1 instead of trusting the model?


r/n8n • • 1d ago

Servers, Hosting, & Tech Stuff spent 40 minutes building an n8n enrichment workflow, then got hit with 4 separate API subscriptions

5 Upvotes

I built an n8n workflow last month that takes domains from a form, checks their traffic, pulls recent LinkedIn and X posts, and finds a verified contact email. It's basically a chain of HTTP request nodes with a bit of filtering and data cleanup in between. Honestly, getting it working wasn't that difficult. The annoying part came when I looked at the pricing for all the APIs behind it. Four different providers, each charging a monthly minimum, even though we're only processing around 50 domains twice a month. Paying for four subscriptions when the workflow sits idle most of the time feels a bit ridiculous.

I started trying to route some of those requests through pay-per-use services instead. Had Monid in a couple of the HTTP nodes while testing, alongside some other options. Ran 70 domains through the workflow on Thursday and the batch finished in roughly six minutes, costing around 3. I did have to add another code node because some smaller websites didn't have an X account, which left empty responses that messed with the next steps. Also had to clean up a few inconsistent fields before the results went into the final sheet. So there's still some work involved, but at least I'm not maintaining four separate monthly plans for occasional lookups.

I'm curious how people here structure workflows like this. Do you generally use separate APIs for each step because they're more reliable, or try to find one provider that covers multiple data sources? And for people using HTTP Request nodes heavily, do you usually handle missing fields and inconsistent responses with separate Code nodes, or is there a cleaner way to build that into the workflow? I'm interested in how others have dealt with this once the workflow moves beyond a small test.


r/n8n • • 1d ago

Workflow - Github Included Workflow: when a target account raises money, changes CEO or lays people off, task the CRM owner automatically (code on GitHub)

1 Upvotes

Disclosure first: I'm the founder of Evinor, the data source this runs on, so weigh accordingly. I'm a software engineer, new to RevOps, and I want to know how this holds up with people who build this for real.

What it does: three Evinor sensors watch one target-account list, using the node @evinor/n8n-nodes-evinor. Funding rounds of $10M or more (2+ outlets), leadership changes (2+ outlets) and layoffs (1 outlet, because you want those early) feed one pipeline:

  1. Normalize each event, then check its confidence band. HIGH continues; MEDIUM and LOW go to a Slack review channel.
  2. Look up the company in HubSpot. If the event has a company domain, match on it. If not, it goes to review instead of guessing.
  3. Owned account: add a timeline note and task the owner. Layoffs go to review so a person decides the tone. Not owned: add a lead row to a Google Sheet.
  4. One Slack digest per day instead of one message per event.

Setup: an Evinor API key, pick one sensor in each trigger node, a HubSpot app token, a custom company property evinor_entity_id, then activate. Free plan: no card, 100 credits per period, up to five sensors and three watchlists. Building and backtesting sensors is free; a delivered match costs credits.

What it doesn't catch yet: domain coverage is uneven, coverage follows press coverage so small private companies are thin, an event can only arrive as early as its first report, and there are nine event types today.

GitHub (JSON, credentials stripped): https://github.com/evinor-ai/evinor-n8n-workflows/blob/main/workflows/hubspot-account-signals/workflow.json

What I'd love to hear from people who build this:

  • Where does your current setup break, and what's the most annoying part?
  • How do you match events to CRM accounts, and how often is it wrong?
  • What would you branch on that I haven't? (roles[] can hold several investors, triggeringReport.sourceKind says article versus first-hand report, reportingOutlets lets you weight by who reported it.)

r/n8n • • 1d ago

Help Hi,

7 Upvotes

I started automation with zapier two weeks with a trial ago but I realised it was going to get expensive, then I started with n8n two weeks ago and built a voice agent with sarvan and automated my sales workflow. Everything is good, I'm hosting on n8n cloud since I am not familiar with self hosting. The workflow executions now estimate to be around 2600 executions per month. So tell me where I will fail and should start watching out. And I built this through Claude connecting n8n, though I tried to be effieicent I still ended up with 8 workflows because Claude told me since the trigger appears very frequent and one depends on another at different times it was needed.


r/n8n • • 2d ago

Servers, Hosting, & Tech Stuff Self-hosted n8n on a 2GB VPS falls over when three workflows run at once. Queue mode or just more RAM?

19 Upvotes

Running n8n in Docker with Postgres on a 2 vCPU, 2GB VPS for my small agency, about 40 active workflows, mostly webhooks plus a few scraping jobs.

Fine most of the day, but when three of the heavier workflows fire together, executions hang, the editor times out and dmesg shows "Out of memory: Killed process (node)". Swap is on, it just gets slow before it dies.

Is this where queue mode with Redis and a worker makes sense, or is that overkill and I should just buy more RAM? What are you running n8n on for client work?

Clients are starting to notice missed webhooks, so I kind of need this fixed this week.


r/n8n • • 1d ago

Workflow - Github Included Built a Confidence-Gated Commercial Lead Router in n8n (Prompt-Injection Screen, 0.85 LLM Threshold & Human Approval Loop)

3 Upvotes

Most AI lead-routing workflows fail in production in two predictable ways: small models get talked into qualifying spam or prompt-injected form submissions, or a malformed LLM JSON response breaks downstream CRM writes.

I built a Confidence-Gated Commercial Lead Router in n8n that pairs a local LLM (Llama 3.2 3B via Ollama, swappable with OpenAI/Anthropic) with deterministic input screening and a human-in-the-loop approval fallback.

How the Architecture Flows:

  1. Dual-Trigger Webhook Entry (Header Auth):

- Path A (/webhook/commercial-lead-inbound): Captures incoming leads, wraps untrusted fields in tagged JSON, and runs an input screen flagging oversized strings (>150 chars), line breaks, {}<> / backticks, or prompt-injection keywords (ignore, system, qualified, confidence).

- Path B (/webhook/commercial-lead-reply): Classifies prospect replies against a strict whitelist (Positive, Question, Not Interested, or Unknown) and drafts a response without ever auto-sending.

2. Confidence Gate (0.85 Threshold + -1 Sentinel Fallback):

- Clean leads scored 0.85–1.00 auto-enroll in the cold-email campaign and log to the CRM (auto_qualified) while reusing the single scoring call.

- Flagged inputs, scores below 0.85, NOT_QUALIFIED leads, or unparseable JSON (-1 sentinel via try/catch) route to an SMTP approval email and pause until a human explicitly approves (default reject on unclear callbacks).

3. Production Error & Secret Safeguards:

- Campaign enrollment uses retryOnFail + error output (30s timeout) so the CRM is never written on a failed enrollment, and admin alerts pass through a redacting formatter that strips api_key= and Bearer tokens.

Architecture, Confidence Matrix & Payload Schemas:

https://github.com/amsnowden2011-source/n8n-automation-workflows/blob/main/commercial-lead-router/README.md

For anyone running LLM-gated routing in n8n: are you relying purely on structured JSON output parsers, or adding regex/heuristic input screens before the model call?


r/n8n • • 1d ago

Workflow - Github Included Claim check v1.2: passive phrasings like "your refund has been processed" now get checked against the tool log

2 Upvotes

Version 1.2 of the claim check is up.

A commenter here asked how the verb list holds up without an LLM. I ran the misses they pointed at. "Your refund has been processed", "the money is back on your card", "invite is out" and "got the refund issued" all used to come back as no claim. Those now extract a claim and get graded against the tool log. "The order was cancelled" and "an email has been sent" already worked.

Another commenter caught that an HTTP 200 with ok:false in the body was counted as success. That is fixed too: the result body is checked, not just the status code.

There is also an optional structured mode. If the agent returns an actions array such as [{"action":"refund","status":"done"}], that list is checked against the tool results directly. The verb list stays as a backstop on the free text.

Same workflow, still no AI key. Code and changelog: https://github.com/SolokitStudio/n8n-agent-ops-templates

It is also in the n8n template library now if you would rather import from there: https://n8n.io/workflows/22987-flag-unsupported-ai-agent-actions-with-slack-alerts-and-google-sheets-logs/

What phrasing would still slip past it? Happy to add test cases.


r/n8n • • 1d ago

Meta & n8n News How are you finding Nod compared to existing agentic systems?

5 Upvotes

I have a soft spot for n8n as it was my gateway into building AI workflows. But over time, I've replaced all of them with vibe-coded apps.

I'm intrigued by the release of Nod, but I've been using Hermes for months (and OpenClaw before) and wonder if Nod offers an advantage in any respect. If so, I'd be keen to check it out. I remember experimenting with the AI Assistant in n8n and finding it incredibly slow. It sounds like Nod is entirely separate from the core n8n product?

I've also been using the major Chinese desktop agents Workbuddy (Tencent) and Qoder (Alibaba), which are both available in English. To be honest, I find them very capable, and you can bring your own API keys.


r/n8n • • 2d ago

Help n8n teaching through projects

7 Upvotes

I m looking for someone who works as freelancer and can help me teach the n8n through projects. I would work for you and you can delegate your tasks to me. I have done btech in computer science with 3 years of experience in prompt engineering


r/n8n • • 2d ago

Workflow - Github Included I built a SOC triage agent in n8n: the AI recommends the action, plain rules decide what needs human approval

2 Upvotes

Hi all,

I built a security triage workflow where an AI Agent investigates events like a junior SOC analyst, but it is not allowed to decide on its own whether a sensitive action may run. Sharing it on GitHub for feedback.

The idea

Security events pile up and most are noise. The agent can do the first look: check the source IP, judge severity, suggest an action. But "isolate this host" or "reset these credentials" should not depend on the model's mood.

How it works

  1. Mock security events arrive: an SSH brute force, a beaconing process, an impossible-travel admin login and an internal scan
  2. Each event is enriched with the criticality of the host (low, medium, high, critical) from a lookup in code
  3. An AI Agent (Gemini) calls a threat_intel_lookup tool with the source IP and returns severity, verdict, action and a one-sentence summary as JSON
  4. A code step validates the answer and applies the approval rule: isolate_host, reset_credentials, and any high or critical severity on a high or critical host are marked needs_approval
  5. An IF node sends those to a Slack approval request, and everything is saved to Postgres

Why the split

The agent suggests, the rule decides. If the model recommends isolating a host, the code still decides whether a human has to look first, and the model can't talk its way around it.

Stack: n8n Cloud, Gemini, Slack, Supabase (Postgres). All free tiers.

What I learned

- Put the approval rule in code, not in the prompt, so it can be audited

- Validate the AI's output before it reaches Slack

- Slack message text must be in Expression mode, or {{ }} shows as plain text

To be clear about the limits: the threat-intel tool is a mock tool with hard-coded data, the demo runs on mock events, and the approval is a Slack message only. Nothing flows back from Slack yet, so no action is executed automatically.

Workflow JSON, setup steps and table SQL:

https://github.com/ztsprofessionalaiid7-alt/autonomous-soc-triage-agent-n8n

Feedback welcome: which signals would you add to the approval rule besides host criticality and severity?


r/n8n • • 2d ago

Servers, Hosting, & Tech Stuff Discovering Nod

2 Upvotes

I built a small n8n workflow with Nod, the open source AI assistant from the n8n Labs team, and the process taught me something about how to work with these tools.

The need was simple: a Google Sheet full of scraped LinkedIn profiles, with duplicates in it. I wanted one clean list in a new tab, without hammering the Google Sheets API, and a single recap email when the run finishes.

Nod's first version was not OK. It wrote a "code" node to normalise the URLs, a chunk of dedupe logic, and even a second branch producing a "duplicate report". Technically fine. More machinery & code than the job needed.

So I pushed back, one thing at a time.

  • "Use the built-in Remove Duplicates node instead of code."
  • "Write into a new tab, and keep the batches small with a pause between them."
  • "One recap email, not one per row." It had to add a Limit node, because the loop's final output carries every row with it.
  • "Don't start if another run of the same workflow is already going." It now checks the running executions before touching anything.

Then it wrote all of that down as a reusable skill, so the next workflow starts with these rules already in place.

👉 One detail I liked as I wanted to implement a "counter":

To use a community node it had never seen before (KeyValue), Nod didn't guess or invent parameters. It read the node's own type definition straight from my n8n instance, which spells out every operation and field: increment, get, reset, the counter name, the step, the start value. Then it checked which of my existing workflows already used that node, to see it in the wild. No public documentation needed, the truth was sitting in the instance all along.

One thing did annoy me though. Nearly every save, the workflow tool grumbled that my canvas had too many separate boxes, and Nod kept wrapping nodes into neat groups to satisfy it. Nothing in the workflow needed those frames. So I said: leave the canvas flat, only group if I ask. That went into the #skill as well.

This one was small: read the rows, dedupe, write, count, one email. Next step is something more complex.


r/n8n • • 2d ago

Now Hiring or Looking for Cofounder Collaboration : expert(e) en automatisation n8n/Make recherché(e) – Missions récurrentes

1 Upvotes

Nous sommes une agence spécialisée dans la conception et le déploiement d'automatisations et d'infrastructures IA sur mesure pour une clientèle B2B.

Grâce à un portefeuille de clients établi et à un réseau solide de partenaires et d'apporteurs d'affaires, nous accompagnons régulièrement des entreprises dans l'optimisation et l'automatisation de leurs processus.

Dans le cadre de notre développement opérationnel, nous recherchons un profil technique expérimenté pour prendre en charge la conception, le développement et la livraison de workflows d'automatisation.

▸ Les missions

Des projets réguliers auprès de nos clients, comprenant notamment :

La conception et le développement de workflows automatisés.

L'intégration d'outils et de solutions SaaS.

La connexion et l'exploitation d'API.

Le déploiement d'infrastructures IA sur mesure.

La maintenance et l'amélioration des automatisations existantes.

▸ La rémunération

Une rémunération attractive composée d'une commission sur chaque projet livré, complétée par une rémunération récurrente mensuelle pour chaque client actif.

Tes revenus récurrents évoluent avec le portefeuille de clients que tu prends en charge.

Les outils, API et bases de données nécessaires sont fournis.

▸ Modalités de paiement

Chaque client bénéficie d'une période de bienvenue avant le début de sa facturation.

Ta rémunération est versée une fois le client entré en facturation, conformément aux modalités définies dans le contrat de collaboration.

▸ Profil recherché

Expérience significative en développement et automatisation.

Excellente maîtrise du front-end ET du back-end.

Très bonne connaissance de n8n et/ou Make.

Expérience concrète dans la conception et la livraison de projets d'automatisation.

Capacité à travailler de manière autonome et à concevoir des solutions fiables, performantes et évolutives.

Disponibilité rapide.

Un portfolio présentant tes réalisations sera indispensable.

▸ Déroulement de la collaboration

Envoi de ton portfolio.

Échange pour discuter de ton expérience et de tes compétences.

Test technique pour évaluer ton niveau.

Signature du contrat si la collaboration est concluante.

✔ Intéressé(e) ?

Nous recherchons un véritable partenaire technique, capable de s'inscrire dans une collaboration durable et de contribuer à la réalisation de projets concrets pour notre clientèle professionnelle.

Si ton profil correspond à nos attentes, envoie-moi ton portfolio en message privé ou directement en commentaire.

site internet


r/n8n • • 2d ago

Servers, Hosting, & Tech Stuff Hey! What's one thing you still REFUSE to automate, even though you probably could with n8n?

11 Upvotes

We spend so much time figuring out what we CAN automate that I think it's interesting to consider what we deliberately choose to keep manual...

Not necessarily because it's technically difficult...

Maybe it's something that requires human judgement, a personal interaction you don't want to lose, or a task where automating it would actually make the experience worse.

I'm wondering -- those of you who have built fairly sophisticated workflows BUT still have certain tasks they prefer doing themselves, where do you personally draw the line? Has there ever been something you automated then eventually decided was better done manually?


r/n8n • • 2d ago

Help n8n whatsapp trigger issue

Thumbnail
gallery
1 Upvotes

I just connect the whatsapp app of mine in meta business suite to n8n's whatsapp trigger node and a send message node too, the problem I am facing is that there are 2 triggers happening completely identical, now its not a status triggers as i turned it off, those are two identical triggers for each message so in reply the agent replies 2 messages again, 2 executions for each message, here are the example executions which are identical in screenshots.

Please tell me a fix please


r/n8n • • 2d ago

Workflow - Github Included My first template submission got rejected as "too basic" — here are the two workflows I built next. What's still missing?

5 Upvotes

A few days ago I submitted a lead-form workflow to the n8n template library. Four nodes: form → code → Google Sheets → Gmail alert. It came back rejected with one line of feedback: too basic to meet the publishing criteria.

Fair enough, honestly. It was a pipe, not a system. I've rebuilt that one (it's back in review), and I changed the standard for everything after it: every stage has to earn its place — validation, a duplicate check, real branching, and something that catches the failure case. These are the next two, and I'd rather get the criticism now than from a reviewer in five days.

1. Inbox Triage (13 nodes) — https://gist.github.com/adevancesystems/e0f202b8cdc704006ddb3cb93caa256d Gmail trigger → rule-based classification (Invoice / Lead / Meeting / Client) with urgency scoring → reads the triage Sheet back and kills duplicates by message ID → logs everything → routes by category: leads get an owner alert plus a draft reply, invoices also land on a finance sheet, client and meeting mail get drafts, high priority fires a Telegram alert. It creates drafts only, never sends.

Two decisions I'm unsure about: (a) keyword classification instead of an AI node — no API key, fully inspectable, but brittle. Feature or limitation for a template? (b) dedup by message ID with a sender+subject fallback — solid enough?

2. Meeting Booker (15 nodes) — https://gist.github.com/adevancesystems/1f9b8325eb85e333d7953276d37e2d21 Booking form → normalize and validate → checks Google Calendar for overlapping events before creating anything → free slot: event created, confirmation sent, booking logged, then a Wait node sends a reminder one hour before → taken slot: no event, the requester gets an email asking for other times, and the clash is logged.

Unsure about: (a) the UTC offset is a constant at the top of the normalize code that the user has to set — acceptable in a template, or a dealbreaker? (b) the reminder relies on a long-running Wait — how do you handle that in templates you share?

What else do you look for in a shared workflow before you'd actually import it? Line-level criticism welcome — that's the point of posting before these go in.


r/n8n • • 2d ago

Servers, Hosting, & Tech Stuff How we solved the "2-second creepy bot" problem in our n8n speed-to-lead AI workflow

1 Upvotes

We have been building inbound speed-to-lead workflows in n8n, and we noticed two big reasons why basic "Form to LLM to SMS" setups fail in production:

  1. Slack alerts alone leave a 60-minute gap. Reps are usually on demos. Pinging a channel does not engage the prospect while they have competitor tabs open.
  2. The 2-second bot giveaway. When an AI sends a 3-paragraph message 2 seconds after a prospect hits submit, buyers ignore it.

Here is the 6-step architecture we use now:

Webhook Idempotency Lock: We hash the email and date in Redis for 10 minutes so double-taps on mobile forms do not fire duplicate SMS messages.

CRM Deduplication First: Query HubSpot/Salesforce before calling OpenAI. Route existing customers directly to their account rep.

Backend Enrichment: We keep forms under 5 fields and let n8n pull company size via HTTP request. The LLM then drops a 3-bullet summary in Slack for the sales rep.

45-Second Wait Node: We delay the first SMS/WhatsApp by 45 seconds. It references the exact problem they typed in the form and asks ONLY ONE question. Max 2 questions before dropping the Cal.com link.

5-Minute Fallback Timer: If the primary rep does not claim the lead in Slack within 5 minutes, n8n reassigns it.

I wrote up the full breakdown (including US TCPA A2P compliance and our exact system prompt) on our engineering blog here:

https://automizehub.ai/blog/speed-to-lead-automation-with-ai-agents-n8n/

How are you guys handling the human takeover switch when a rep jumps into an active AI WhatsApp thread?


r/n8n • • 2d ago

Help Disappointed with n8n’s new self-hosted pricing structure

8 Upvotes

I've been a huge supporter of n8n for quite some time. I've told countless teams about it, praised its features, and used it to create some of my best workflows.

That’s why it’s frustrating for me to say this:

The new Business tier for self-hosting really misses the mark when it comes to the needs of users who run high volumes.

Sure, the Community Edition is still free, which is fantastic. And yes, there are Enterprise options for teams that need premium support.

But now, there's this Business plan for self-hosted users that charges based on executions, similar to the cloud model.

Here’s the issue:

When you self-host, you’re using your own infrastructure. You handle the costs of compute, bandwidth, storage, and maintenance. So why are we being charged again for each execution?

At around a million executions a month, which would cover just one of our current setups, I’d be looking at:

$10,400 every month

$124,800 annually

...for software that operates on servers I’m already funding.

Now multiply that by the five instances I run, and it becomes utterly unmanageable.

This isn't about being frugal. I genuinely want to support quality tools. But this pricing structure penalizes successful usage and undermines the key benefit of self-hosting: managing costs and having freedom.

Think about it: if Supabase charged you for every query on a self-hosted setup, no one would accept that. n8n is doing something similar with CPU cycles that we provide.

If you’re going to impose cloud fees, then you better be delivering a cloud service.

I’d be totally fine with paying a per-user fee, but not for executions on my own servers.

I still see a lot of potential in n8n and want to continue supporting it.

However, if this pricing model is here to stay, I’ll have to reconsider recommending it and start looking into options that align better with the self-hosting cost structure.

What really baffles me is this: I can have unlimited executions on the free Community tier, but if I switch to the Business plan, that changes? Can someone from n8n please explain this to me?