r/n8n • • 6d 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 • • 27d ago

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

27 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


r/n8n • • 3h 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?

4 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 • • 10m ago

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

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

Help n8n teaching through projects

2 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 • • 1h ago

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

1 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 • • 2h ago

Servers, Hosting, & Tech Stuff Discovering Nod

1 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 • • 2h 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 • • 4h 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 • • 16h ago

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

9 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 • • 14h 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 • • 6h 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 • • 22h 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?


r/n8n • • 12h ago

Help Looking for a working Claude Pro 7-day Guest Pass

1 Upvotes

Hey everyone! 👋 I'm currently exploring Claude Pro for AI agent development and would love to try it out before subscribing. Does anyone have a working 7-day free trial Guest Pass or referral link they could share? I'd really appreciate the help! Please send me a private message (DM) if you have an available invite. Thanks a lot! 🙏


r/n8n • • 16h ago

Workflow - Github Included WhatsApp appointment reminders using native polls instead of free-text parsing (Google Sheets + Google Calendar)

2 Upvotes

Parsing free-text WhatsApp replies for appointment reminders is a trap. Put an LLM or a keyword router in front of "yes", "actually can we do tomorrow", a thumbs-up reaction, or a 12-second voice note, and sooner or later it misreads a message and deletes a real booking.

Native WhatsApp polls avoid that whole mess because the user taps one of three fixed options and the webhook returns an integer index (0, 1, or 2) tied to the original poll message ID.

Here is how the workflow is wired up across two triggers:

  1. Daily reminder pass (Schedule Trigger -> Google Sheets -> WhatsApp Poll): Pulls rows marked Scheduled, normalizes phone numbers, sends a 3-option WhatsApp poll (Confirm appointment, Move +24 hours, Cancel appointment), and writes the returned pollMessageId back into the sheet row. Keying by pollMessageId instead of phone number means someone with two upcoming appointments never updates the wrong one.

  2. Real-time vote handler (Trigger on vote -> Google Sheets lookup -> Switch): Looks up the booking row by pollMessageId and branches on selectedOptionIndices[0]:

    • 0 marks the row Confirmed and sends a short confirmation reply.

    • 1 fetches the existing Google Calendar event, shifts start and end forward by 24 hours, updates both Google Calendar and the sheet row, and replies with the new slot.

    • 2 deletes the Google Calendar event, marks the row Cancelled, confirms to the customer, and pings an internal staff WhatsApp group so the open slot can be filled.

It uses the n8n-nodes-supergreen community node (verified on n8n Cloud, also works self-hosted) since Meta's Cloud API doesn't let you send native WhatsApp polls or post into regular staff groups without template pre-approval.


r/n8n • • 22h ago

Help Marketer with 5+ years of experience looking to pivot into workflow automation. Any advice?

4 Upvotes

Hi everyone!

I'm a marketer with 5+ years of experience, mostly as a generalist who's touched nearly every part of the marketing pipeline. I'm at a point where I really want to specialize and build a more technical skill set.

Lately, I've been exploring workflow automations and SEO/AEO. I've started applying what I'm learning to my own e-commerce website to get hands-on experience, measure real results, and build a portfolio.

I'm still figuring out if this is the right direction and would love advice from anyone who's made a similar pivot. What skills or tools should I prioritize? Are there specific roles I should be looking into?

I'm also open to internships, apprenticeships, mentorship, or any opportunities to learn. I don't necessarily want to start from scratch, but I'm willing to put in the work.

Apologies if you see this in multiple subreddits! Genuinely just looking for insight and guidance. Here to listen and learn!


r/n8n • • 20h ago

Help if you are building automation with voice agents, how do u handle call-drop scenario? Do u manually dry-run those cases urself?

1 Upvotes

if u are automating using voice agents, how do u handle call-drop situtation or bad network scenarios?


r/n8n • • 1d ago

Help Looking for a technical co-founder / partner to build AI-powered sales automation systems for B2B SMBs

4 Upvotes

Hey everyone,

I'm based in India and exploring an opportunity to build practical AI-powered sales and GTM automation solutions for small B2B businesses. I'm looking for someone with strong technical skills who is interested in building a business together as a serious, long-term partnership.

A little about me:

My primary interests are in GTM, product marketing and sales strategy. I've worked on ICP research, positioning, value propositions, competitive analysis, inbound, ABM, outbound and customer acquisition through independent case studies and practical project exposure.

I've also gained experience in account research, prospect qualification and buying-signal-based outbound research through a supervised project.

I'm still early in my journey and don't claim to have built or scaled a company. I'm actively researching business problems and looking for a genuine opportunity to solve.

What I'm exploring:

I want to help small B2B businesses improve their outbound sales processes, particularly the research and qualification work before outreach.

One direction is an account-based prospecting system that can:

- Discover potential companies or work with existing prospect lists.

- Enrich accounts with relevant business information.

- Evaluate companies against a specific ICP.

- Identify buying signals, hiring, expansion, technology changes and potential switching opportunities.

- Prioritise accounts based on fit, timing and relevance.

- Prepare personalised, evidence-backed outbound campaigns and automate parts of the process.

The goal is to help businesses find fewer, better-qualified accounts and approach them at the right time, rather than simply generating more leads and sending more emails.

I'm not fixed on building this exact product from day one. I'd rather understand real business workflows, identify problems worth solving and build around actual customer needs.

Who I'm looking for:

Someone who can independently own the technical side and build actual working systems. Relevant experience includes:

- n8n, Make or similar workflow automation tools.

- Python / JavaScript, backend development, APIs and integrations.

- Web scraping, data extraction and company enrichment.

- Data pipelines, databases and external data sources.

- AI agents, LLM integrations, MCP and tool orchestration.

You don't need to know every tool listed. What matters is being able to solve technical problems independently and build reliable systems beyond basic automation demos. Experience with data extraction, enrichment and real-time monitoring would be especially useful.

A few things I'd like to know about you:

- What have you actually built? Portfolio, GitHub or working demos would be helpful.

- What technologies do you work with?

- Have you built anything involving data extraction, enrichment, APIs or AI automation?

- Are you interested in building a business or product long-term?

I'm open to connecting with people from India or elsewhere. Technical capability, ownership and genuine commitment matter most.

If this interests you, feel free to comment or DM me. I'd be happy to share more about my research and explore whether there's a genuine fit.


r/n8n • • 1d ago

Help If you charge clients a monthly maintenance fee: has a client ever asked what they're paying for?

5 Upvotes

For those who keep client automations running on a monthly fee, not one-off builds. I'm trying to understand how others handle this:

  1. Roughly what do you charge per month, and for how many workflows?

  2. Has a client ever questioned the fee, or cancelled, in a quiet month when nothing broke? What happened?

  3. Do you send them anything each month to show what you did? What's in it, and how long does it take you?

Rough numbers are fine. Thanks.


r/n8n • • 1d ago

Help How we automated lead routing and CRM sync using n8n to eliminate response delays

0 Upvotes

Hey everyone,

We recently ran into a common bottleneck with lead capture: potential clients filling out forms on landing pages, but manual data entry causing delays before getting a response.

To solve this, we set up an n8n workflow that handles it end-to-end:

  1. Captures form data instantly.

  2. Validates and routes the lead.

  3. Syncs directly with the CRM / Google Sheets.

  4. Sends a real-time alert via Telegram or WhatsApp to the team.

Has anyone implemented something similar? I'm curious what error-handling nodes you use when the CRM API drops connection temporarily.


r/n8n • • 1d ago

Help What are the most useful phone agents to use with Meta's new Muse?

9 Upvotes

Been playing around with Meta's Muse for a few days and want to pair it with something that can actually handle calls, not just chat. My setup right now is pretty basic and i'm not sure which phone agent layer makes sense to sit on top of it.

Do i need something purpose-built for voice or will a general ai agent hold up? Anyone running Muse with a phone agent already? Curious what's actually working.


r/n8n • • 1d ago

Workflow - Github Included I built a demand forecast and reorder workflow in n8n: rules forecast, an AI Agent recommends the order (Gemini, Slack, Postgres)

0 Upvotes

Hi all,

I built a supply chain workflow that finds products running low and recommends what to reorder. Sharing it on GitHub for feedback.

The idea

Forecasting is arithmetic, so I kept it in code. The AI only does the part that needs judgement: how much to order, how urgent it is, and what to tell the supplier.

How it works

  1. Inventory data comes in (stock, supplier lead time, sales of the last 4 weeks). The demo uses 4 mock products

  2. A code step forecasts weekly demand (average plus trend), the reorder point and the days of cover

  3. An IF node lets only products at or below the reorder point reach the AI, so healthy stock costs no AI call

  4. An AI Agent (Gemini) returns the reorder quantity (about 6 weeks of demand), an urgency level and a short note for the supplier, as JSON

  5. A code step validates the answer (whole numbers, allowed urgency values only), then a Slack alert goes out and everything is saved to Postgres

Why the split

The numbers are deterministic, so I can show exactly why a product was flagged. The model never decides whether something needs a reorder, it only advises on the order itself.

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

What I learned

- Filter before the AI call: it saves quota and keeps results consistent

- Validate AI output in code before it reaches Slack

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

To be clear, the AI Agent node has no tools here, just a structured JSON answer, and the demo runs on mock data.

Workflow JSON, setup steps and table SQL:

https://github.com/ztsprofessionalaiid7-alt/supply-chain-reorder-agent-n8n

Feedback welcome: would you add seasonality to the forecast first, or supplier reliability?


r/n8n • • 1d ago

Workflow - Github Included Free n8n workflow: drop a video in Google Drive → auto-posted to TikTok, Reels & Shorts

Post image
2 Upvotes

Uploading the same short video to 3 apps every day got old, so I automated it.

Workflow (free): https://gist.github.com/cxd3rev/70b72fb043e12d28fa1ed57af6b06826

How it works:

  1. Drop a vertical video in a Google Drive folder

  2. n8n downloads it and posts it to TikTok, Instagram Reels and YouTube Shorts via Upload-Post

  3. The file name becomes the caption

Two gotchas I hit:

- YouTube rejects titles over 100 chars, and Upload-Post then cancels ALL platforms. The workflow cuts the title for you.

- Upload-Post's "user" field wants the profile's internal name (mine was "default"), not the display name.

I also made a full version with a Telegram Approve/Skip step before anything goes live, error alerts and a PDF guide (link in comments). Happy to answer setup questions!


r/n8n • • 1d ago

Help Looking for n8n users to beta test my app (turn your workflows into sellable SaaS)

2 Upvotes

Hey everyone,

I’m looking for a few n8n users who’d be willing to test the product and give honest feedback.

What it does

You upload your n8n workflow (.json), and app turns it into a ready-to-sell SaaS product with:

  • A clean frontend for your users

  • Built-in payments (Stripe)

  • Multi-user support

  • Instant deployment

Basically: take the automations you already build → package them → start charging for them.

Who I’m looking for

  • People who regularly build n8n workflows

  • Ideally people who have thought about productizing their automations (or already sell services)

  • Willing to spend 20–40 minutes testing and sharing feedback

What you’ll get

  • Free access during the beta

  • Direct line to me (I’ll actually listen and implement good feedback)

  • Early access + discount if/when it launches publicly

If you’re interested, just comment or DM me and I’ll send you access.

Thanks a lot — really appreciate any help from the n8n community 🙏


r/n8n • • 2d ago

Help Mixing Seedance 2.5 and Kling 4.0 in one n8n batch: where do you validate each row before it costs money?

3 Upvotes

Batch video in n8n is easy until the sheet has more than one model in it. A row that’s fine for one video model is a 400 error, or worse a valid but wrong render, for another.

Concrete example: each row is a prompt, a model, a duration, a resolution, audio on/off and a reference image. Some rows go to Seedance 2.5, some to Kling 4.0. The differences that bite:

- Duration rules aren’t the same. Kling 4.0 is documented as 3 to 30 seconds per generation; other models accept a narrower range or a fixed set of values. A 12 that’s valid for one row can be rejected or rounded for the next.

- Audio isn’t free. On several models, turning audio on moves the job to a different price tier, so one column someone flipped to yes changes the cost of the whole run.

- References don’t share a schema. First frame, last frame, keyframes, reference images and reference videos use different fields, and the limits differ per model.

- Async jobs fail late. Submit returns 200, the job fails or gets filtered minutes later, and unless the poll step writes that back to the row, every node is green.

The post here a couple of weeks ago about batch-generating Veo from a Sheet covered claiming rows and never resending a timed-out submit, which I’d keep as-is. What I’m stuck on is validation before submit. Options I can think of:

  1. A Code node with a per-model rules table (allowed durations, max refs, audio flag) that rejects the row with a reason before any HTTP call.

  2. Normalizing through one provider layer, whether that’s fal, Replicate or ĠPȚ pro,to, so the request body is closer to one shape, and keeping only model-specific limits in the table.

  3. A cheap short test render per row first, and only queuing the full length if it passes.

Option 1 feels right, but the table goes stale every time a model updates.

If you run mixed-model video batches in n8n, where does your validation live, and how do you keep the limits current?