r/n8n • • 11h ago

Help How are you using n8n for marketing operations/automation

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

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

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

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

3 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 • • 8h ago

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

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

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

3 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 • • 1d 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 • • 16h 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

1 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 • • 1d ago

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

6 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 • • 18h 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 • • 1d ago

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

4 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.


r/n8n • • 1d 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)

1 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:

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 • • 1d ago

Workflow - Github Included Built an invoice chaser in n8n where the AI writes the emails and reads the replies, but a Code node decides every next step (repo inside)

0 Upvotes

After the invoice checker I wanted to try the other side of the money problem, chasing invoices that are already late, so I built an n8n agent that does it for a small business. Every morning it picks the invoices whose next step is due and writes each client a reminder in the owner's voice, a heads-up before the due date and then a little firmer each time it's late, and when a client writes back it reads the reply and decides what happens next.

The part I cared about most was keeping the AI away from anything that matters. The model only writes the email text and labels the reply as one of seven types, like a promise to pay, already paid or a dispute, and it returns that through the Messages API with a JSON schema. Everything after that is a Code node with fixed rules, so a promise to pay pauses the reminders until that date, "we already paid" asks the owner to check the bank instead of sending another reminder, and a dispute stops everything and goes to the owner. The AI never moves a due date or changes an amount on its own, and if the AI call fails a plain template is used so a reminder is never skipped.

It's five workflows: setup with Data Tables and demo data, the daily chaser on a Schedule Trigger, the reply reader, the dashboard pages and a Monday summary. There's a demo mode and a test mode, so nothing reaches a real client by accident while you try it.

One thing that took me a while on the dashboard: I wanted a button that runs the agent and lands the browser back on the updated page with no polling. What worked was a Webhook set to respond when the last node finishes, with response data set to no data, a custom 303 code and a static Location header, so the browser just waits while it runs and gets one redirect. A Respond to Webhook node with a dynamic Location only worked once I switched the webhook to the "Using Respond to Webhook node" mode.

Repo with the workflows, the Code node source and setup steps: https://github.com/Mangel-bit/n8n-invoice-chaser

I'm curious how others would handle replies that mix things, like "we'll pay half on Friday but the second line looks wrong", whether you'd split it into two actions or just hand it to a person.


r/n8n • • 1d ago

Help Need help with creating a Google Calendar --> Sheets/ or Docs--> NotebookLM pipeline

3 Upvotes

I know I have to attach an ics file in somehow but the only advice I found is a 13 year old thread on stackoverflow which is no help. The sheets/ or docs to notebook lm pipeline is easy to solve because it's literally just importing the source into notebooklm. The trouble is creating a script that uses an uncompressed ics file so it can be directly read by notebooklm in sheets or docs. Then letting n8n insert that file as some sort of chip or directly read it as text and then put into a cell in sheets or docs. Then notebookLM reads it. tell me if there is anything wrong in my thinking.


r/n8n • • 1d ago

Workflow - Github Included I automated 20+ Telegram job channels using n8n, Gemini, and Google Sheets (5 → 20 posts/day

2 Upvotes

I run Telegram job channels for 20+ cities. Posting vacancies manually used to take ~30 min/day, and nothing went out at night or on weekends.

I rebuilt the entire pipeline in n8n so it runs on autopilot.

How it works:

  1. Trigger & Config: A Schedule Trigger kicks off the main workflow. A Set (config) node holds the array of cities — adding a new city is literally one line.

  2. Scraping: HTTP Request + HTML Extract scrape the job portal’s listing pages.

  3. Deduplication: Job IDs are checked against a Google Sheet to skip already processed listings.

  4. AI Formatting: Gemini API rewrites each raw description into a clean, consistent Telegram post.

  5. Queueing: Processed posts are saved to Google Sheets acting as a queue, with a calculated publish timestamp per post.

  6. Publishing: A second workflow polls the sheet and posts to Telegram only during working hours, using randomized delays between messages.

Results:

  • Output: 5 → 20 posts/day

  • Manual work: ~30 min/day → ~5 min/day (just monitoring)

  • Scale: 20+ city channels running 24/7

What I learned (the hard way):

  • Rate limits matter: Wait nodes and random delays are mandatory if you don't want to get IP-banned by the source portal or hit Telegram API limits.

  • Sheets as a queue > direct posting: Decoupling scraping from publishing via Google Sheets makes debugging 10x easier and prevents losing scraped data if Telegram or Gemini hiccups.

  • Lock down the prompt: Keep the Gemini system prompt super strict (with explicit formatting examples), otherwise the tone and emoji usage start drifting across posts.

Happy to share the JSON workflow structure or answer questions about the setup!

https://gist.github.com/ai-assist-io/db12db4a615619b44c8c15ada9c94001

Stack: n8n, Google Gemini API, Google Sheets, Telegram Bot API, Web Scraping.


r/n8n • • 2d ago

Servers, Hosting, & Tech Stuff Why my approval webhook kept leaving people with a spinning browser

5 Upvotes

👋 Hey n8n Community,

Been building a multi-step approval system, one-click approve and reject links in emails, tokens, the usual. Three things caught me out.

Email security scanners pre-fetch your links. Corporate mail filters follow URLs to check them before the recipient ever sees the message. If your approve link is a single-use token, the scanner burns it. Approvers also double-click buttons. Either way the second request finds the token already consumed.

Which then hangs the browser. When my Postgres lookup found no row, it returned zero items, and a node with no input items just does not run. So Respond to Webhook was never reached and the user sat watching a spinner until timeout. The fix is Always Output Data on the lookup node, so an empty item flows through and a guard node can classify it as not found, invalid or already processed, then return a proper “this link is no longer active” page. Worth knowing it is documented not to set this on IF nodes.

Inside a loop, .first() always gives you item zero. Batch approving three requests generated three PDFs for the first one, because every expression inside the loop referenced $('Node').first(). Switching to .item made each iteration use its own row. Obvious once you see it, invisible until you do.

One more that is less of a gotcha and more of a design change: PDF generation took several seconds per item, so holding the webhook open meant a spinner after every click. Responding immediately and letting the loop run on afterwards made the portal feel instant.

Anyone else dealt with scanners eating single-use tokens? Curious whether people just accept it and make links idempotent instead.

Best,
Felix


r/n8n • • 1d ago

Help Evolution API: one instance goes “connected but deaf” right after another instance reconnects. Anyone seen this?

1 Upvotes

Hi all, I’m running a self-hosted Evolution API v2.3.7 (Baileys) in Docker, with the webhook (MESSAGES_UPSERT) going to n8n. It’s my first real client: a WhatsApp ordering bot for a small burger shop.

There are 2 instances on the same Evolution container:

  • Store: the client’s number. Busy account, lots of customers posting status updates.

  • Demo: my own test number. Almost no traffic.

The problem: the store instance stops receiving messages. connectionState still says “open”, there are no errors in the logs at that moment, and no logout. Restarting the instance doesn’t help. Only logout + pairing again fixes it.

The pattern I found in the logs (local time):

  • Day 1: demo reconnects at 16:48, store reconnects at 16:51, store goes silent at 16:52.

  • Day 2: I re-paired the store at 09:00 and it worked all day. Demo reconnects at 16:44, store goes silent at 16:48.

So both days, the store died a few minutes after the demo instance reconnected on its own.

Other things I noticed:

  • Before re-pairing, the store instance was reconnecting every 50 minutes, and messages arrived late, in batches.

  • About every 50 minutes there’s a stream errored out error with ack class=status type=media, even while things were working fine.

  • Setting: groupsIgnore true, readStatus false, readMessages false, syncFullHistory false.

  • The store phone also has another linked device (WhatsApp Web on a PC).

My questions:

  1. Has anyone seen one instance’s reconnect break another instance on the same server?

  2. Is it better to run each number in its own Evolution container?

  3. Or is this just Baileys being Baileys, and the real fix is moving to the official Cloud API?

My next test is to disconnect the demo and see if the store survives past 17:00. I’ll update the post with the result.

Thanks!


r/n8n • • 1d ago

Help N8N - Hotel Revenue Management Workflows

0 Upvotes

Hello all!

I am completely new in the group. The reason I joined is because Chatgpt recommended me n8n for automation workflows. However, I am bit confused. What is the difference between Hubspot and n8n and how i can maximize n8n potential.

To begin with, I am working in Hotel Revenue Management, in Athens, and I want to enhance my role responsibilities and build agents and workflows in order to build a system. A system which may helps define commercial decisions.

However, I am not sure how to start or where to start from. Is there anyone, who has already done in for the specific industry or any other similar and would like to share? I would really use a help.

Chatgpt and Claude recommended to use n9n, but I am bit confused.

I am working for a Hotel revenue management agency and I want to find ways to improve and automate my daily working routine.

Overall, an example from any other industry would be beneficial enough, especially to understand the structures and the outcomes.

Thank you all in advance 🙏🏻


r/n8n • • 2d ago

Help Microsoft login for an app hosted in n8n

5 Upvotes

I built an internal app on n8n Cloud. A webhook serves an HTML page, and the page calls other webhooks that read and write our SQL database through Power Automate. Each user’s rights come from a security table in that database, looked up by email address.

The problem is login. n8n Cloud can’t put a webhook behind a Microsoft login, so for now people type their mail plus a shared password. That means anyone with the password can sign in as a colleague and approve things in their name, so it is by far not safe.

Is there a way to add Microsoft Entra ID login to the HTML page, so n8n knows for sure who is calling?


r/n8n • • 1d ago

Workflow - Github Included Lead-brief workflow: one input (domain/URL/email) -> three HTTP calls -> merged object + short text brief (JSON on GitHub)

2 Upvotes

Sharing a small workflow I use for quick lead research. It takes one input (a domain, URL or email, via manual trigger or a webhook POST like {"input": "acme.com"}), fans out to three HTTP Request nodes, merges the results in a Code node, and returns one object plus a short text brief.

Workflow JSON (GitHub gist): https://gist.github.com/kingefman1-cmyk/6a5ab9338c52d4607e30fdc8ccf79e50

Structure:

  • Trigger: Manual + Webhook, normalised in a Code node (strips protocol, detects email vs domain)

  • 3 parallel HTTP Request nodes: company info (title/description, JSON-LD org, social links, DNS/MX), email check (syntax, MX/SPF/DMARC, free/disposable flags, score), page SEO basics (canonical, lang, headings, OG image)

  • Merge + Code node: builds one JSON object and a plain-text brief; each source gets a status field so a failed call shows up as "failed" instead of breaking the run

Example of the brief for cloudflare.com:

LEAD BRIEF: Cloudflare
Website: https://www.cloudflare.com/
Email check: domain-level only (no address supplied, checked postmaster@) | deliverability 100/100
Mail security: SPF yes, DMARC yes
Data status: company_intel=ok, lead_verify=ok, seo_xray=ok

Disclosure: the three HTTP nodes point at an API I run, and they need a key in the Config node (there is a small free tier for testing). The nodes are plain HTTP Request + Code, so you can point them at any equivalent endpoints you already use and keep the structure.

Happy to take feedback on the merge logic or the brief format.


r/n8n • • 2d 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
5 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 • • 2d ago

Workflow - Github Included LLM-as-Judge eval pipeline in n8n: two independent judges

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 • • 2d ago

Workflow - Github Included Free n8n workflow: Enrich B2B company domains (emails, tech stack, ATS hiring, DMARC, llms.txt & buying score) in 1 HTTP call

3 Upvotes

Sharing a lightweight n8n workflow I put together for B2B lead enrichment so you don't have to chain 4–5 separate scrapers for every domain. What the workflow does:

  1. Accepts raw domains (stripe.com), full URLs, or even work emails ([email protected]) — auto-normalized & deduplicated.

  2. Makes 1 HTTP Request that extracts:

    • Business emails (including Cloudflare-obfuscated emails) & social links

    • Tech & ad stack (65+ HTML/header signatures + DNS SPF-verified tools like HubSpot/Postmark/Zendesk)

    • Hiring status + 15 ATS detectors (Greenhouse, Lever, Ashby, Workable, etc.)

    • Pricing page & model (freemium, free-trial, self-serve, contact-sales) + blog/changelog freshness

    • Live DNS (MX email provider, SPF, DMARC), SSL expiry, /llms.txt, robots.txt AI bot rules & SEO score

    • A 0–100 buyingSignalScore + human-readable buyingSignals array for AI cold email prompts

  3. Filters buyingSignalScore >= 60 and formats a clean outreach brief ready for Slack, Google Sheets, or OpenAI. Free importable n8n JSON: https://gist.github.com/oguzhankiran/245507d4a92e42c17f93781fe0400158 Full disclosure: It uses an Apify Actor I built (kiranvia/b2b-company-intelligence — https://apify.com/kiranvia/b2b-company-intelligence) running zero-browser at 256 MB RAM, so Apify's free monthly credits are enough to test it on hundreds of domains. If anyone tests it and notices a missing ATS or tech stack signature they need for their workflow, drop a comment and I'll add it!


r/n8n • • 2d 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)

3 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 • • 3d 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.

2. 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.

3. 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 • • 2d 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?