The Underdog AI Automation Stack
You don't need an expensive SaaS for every task. With just n8n and Claude, marketers can wire up WhatsApp alerts, payment notifications, the Conversions API, lead capture, and AI auto-replies — self-hosted and almost free. Here are five workflows you can steal.
- The Systems Summary
- Why n8n + Claude Is the Underdog Stack
- The 5 Automations, Mapped Out
- But Where Do You Actually Need Claude?
- 1. Send WhatsApp Messages Straight From the API
- 2. Customer Payment Intimation (Razorpay)
- 3. Set Up the Meta Conversions API (CAPI)
- 4. Collect Leads From Landing Pages Into Any CRM
- 5. Let Claude Auto-Reply to Customer Messages
- Frequently Asked Questions
The Systems Summary
You don't need a paid tool for every marketing task. Two underdogs — n8n (an open-source, self-hostable automation platform) and Claude (the AI brain) — cover most of what marketers pay a dozen SaaS subscriptions for. In this guide you get five ready-to-steal workflows: (1) send WhatsApp messages via the API, (2) intimate Razorpay payments across WhatsApp, email, and Slack, (3) run the Meta Conversions API, (4) capture landing-page leads into any CRM, and (5) let Claude auto-reply to customer messages. Cheap, self-hosted, and yours to own.
Why n8n + Claude Is the Underdog Stack
Most marketers stitch together five or six paid tools to do what a single n8n instance can handle. n8n is open-source, self-hostable, and connects to almost anything — WhatsApp, Razorpay, Meta, Google Sheets, Slack — without per-task fees. Pair it with Claude for the "thinking" steps (writing, replying, summarising) and you have a full automation stack that costs a fraction of the SaaS bundle it replaces.
The best part: you own the pipes. No vendor lock-in, no per-event pricing that punishes you for growing, and no data leaving your control. That is why it is the underdog — quietly more powerful than the tools that outspend it on marketing.
Pro-Tip
Start by self-hosting n8n on a cheap cloud instance (or n8n Cloud if you'd rather not manage servers). One instance can run every workflow in this guide at once.
The 5 Automations, Mapped Out
Every workflow below follows the same shape: a trigger fires, n8n routes it, and one or more actions happen — with Claude stepping in wherever thinking is needed. Click each use case to see its exact flow, tools, and a real example:
The n8n + Claude Stack
5 Automations Marketers Can StealWhatsApp Messaging
How It Works
n8n has a native WhatsApp Business Cloud API node. Grab an access token and phone number ID (WABA) from Meta for Developers, connect it once, and any workflow can fire WhatsApp messages — no paid third-party tool sitting in between.
The Flow
Tools
Example
A customer submits a form and instantly gets a WhatsApp message with their next steps — sent by your own workflow, not a subscription service.
But Where Do You Actually Need Claude?
Look at the five workflows above and you might think most of it is just n8n plumbing — so where does Claude actually come in? Two places, and the first one is the whole reason this stack works even if you are not technical.
1. Claude builds the automations with you. Honest truth: I am not an n8n expert. The moment a workflow needs a Function (Code) node, a fiddly expression, or a bit of JavaScript to reshape data, I used to get stuck. Now I do not wrestle with that technicality at all — I simply describe the requirement to Claude in plain English (for example, "take the Razorpay webhook and send the customer name and amount into this WhatsApp template"), and Claude tells me exactly which nodes to use and writes the code that goes inside the Function node. If a node throws an error, I paste it back and Claude fixes it. Claude is the reason someone who is not a technical n8n user can still build every workflow on this page.
2. Claude is the brain inside the workflow. That is use case 5 — at runtime, Claude reads a customer message and writes the reply. And the same idea drops into any workflow that needs a judgement call: summarising a lead, cleaning up messy data, or drafting a follow-up.
So even the "simple", n8n-only workflows are really n8n + Claude — you are just leaning on Claude at build time instead of run time.
Pro-Tip
When you ask Claude for help, paste the sample data that n8n shows you (the JSON from the previous node) and name the two nodes you are working between. Claude will write the Function-node code against your real field names instead of guessing.
1. Send WhatsApp Messages Straight From the API
n8n ships with a native WhatsApp Business Cloud API integration, so you can send WhatsApp messages directly from your workflows — no third-party messaging SaaS in the middle. Setup is genuinely simple: from the Meta for Developers documentation, collect two things — an access token and your phone number ID (WABA ID) — plug them into the n8n WhatsApp node, and you're live.
Once connected, any trigger in n8n can send a WhatsApp message: a form submission, a new order, a scheduled reminder — anything.
Pro-Tip
WhatsApp requires pre-approved message templates for business-initiated messages. Approve a few reusable templates (welcome, reminder, confirmation) once, and reference them from any workflow.
2. Customer Payment Intimation (Razorpay)
When a customer pays through Razorpay, Razorpay fires a payment webhook. Point that webhook at n8n and you can intimate everyone who needs to know, instantly and in parallel:
• WhatsApp the customer a payment confirmation right away.
• Email the customer a receipt or invoice right away.
• Ping your internal operations team on Slack so they can start fulfilment right away.
One event in, three notifications out — no one refreshing a dashboard, no missed orders.
Pro-Tip
Add a filter node so only "payment.captured" events trigger the flow — that way failed or pending payments don't fire false confirmations.
3. Set Up the Meta Conversions API (CAPI)
Sending server-side conversion data to Meta is what keeps your ads optimizing in 2026 — and you don't need an expensive subscription to do it. Instead of a per-event SaaS bill, run the Conversions API inside n8n using a ready-made template. It's the exact same template we shared in our Meta ads guide: clone the n8n CAPI template, drop in your dataset ID and access token, and your checkout events start flowing straight to Meta.
You self-host it, you own it, and you pay once for hosting instead of forever per conversion.
Pro-Tip
Share the same event_id between your browser Pixel and this server-side CAPI flow so Meta deduplicates the conversion instead of counting it twice.
4. Collect Leads From Landing Pages Into Any CRM
Build a landing page, point its form at an n8n webhook, and every submission is captured automatically and sent to the CRM or store of your choice. You are not locked into one tool — route the lead to whatever you actually use:
• Google Sheets for a simple, shareable list.
• Airtable for a light CRM with views and automations.
• Supabase (or any database) when you want to own the data.
The result is clean lead management: no manual copy-paste, no leads lost between the form and your follow-up, and full freedom to switch tools later without rebuilding your funnel.
Pro-Tip
Add a Claude step here to auto-tag each lead (hot / warm / cold) or write a one-line summary before it hits your CRM — a tiny upgrade that saves your sales team real time.
5. Let Claude Auto-Reply to Customer Messages
This is the low-hanging Claude win, and it stays just as simple as the four workflows above. When a customer message arrives — a WhatsApp text, an Instagram DM, or an email — n8n hands it to Claude, which reads it, writes a helpful and on-brand reply, and either sends it back automatically or saves it as a draft for you to approve.
It's one trigger, one AI step, one action: message in → Claude → reply out. Your inbox starts answering the easy, repetitive questions on its own, so you only step in when it actually matters.
Pro-Tip
Start in "draft mode" — have Claude write the reply but leave sending to a human. Once you trust the quality on your real questions, flip it to auto-send for the simple ones.
Frequently Asked Questions
Official Documentation & Sources
