Growth Infrastructure

This One AI Workflow Runs My Entire Business

One customer payment triggers a single n8n workflow — built entirely with Claude — that thanks the customer, stores their data, onboards them, unlocks their course in Moodle, books calls, and feeds the ad platform. Here is the whole thing, mapped out.

Table of Contents
Quick Navigate:The SummaryOne TriggerThe Full WorkflowSmart BranchingBuilt by ClaudeFAQs

The Systems Summary

I don't have a big operations team running my back office — I have one n8n workflow, built entirely with Claude. The instant a customer pays, it fires: the customer gets a thank-you on WhatsApp, their details are stored in a central database, and then the workflow branches based on what they bought — course buyers get onboarding + an automatic Moodle unlock, service clients get a detailed intake form, and consultation bookings get a calendar invite. Every sale is also pushed to the ad platform via the Conversions API. One payment in, an entire business running itself out.

It All Starts With One Trigger: A Payment

The entire system hangs off a single event: a customer payment. When the payment succeeds, the payment gateway fires a webhook into n8n, and that one signal kicks off everything else. There is no dashboard I log into, no list I work through, and no "I'll get to it tomorrow." The workflow does in seconds what used to be a scattered checklist of manual tasks — and it does the same thing, flawlessly, at 3pm or 3am.

Pro-Tip

Anchor your automation to the most reliable event you have. A confirmed payment is perfect — it only fires for real customers, so every downstream action is safe to run automatically.

The Full Workflow, Mapped Out

Here is the actual shape of it: one payment at the top, fanning out into every outcome that keeps a customer happy and my business running. Click any node to see exactly what it does, which tools it touches, and why it matters:

One Payment → Everything Runs

A single n8n workflow, built with Claude

Thank-You on WhatsApp

Instant confirmation, premium first impression
What Happens

The moment a payment lands, the customer gets a warm thank-you message on WhatsApp. No waiting, no wondering whether it went through — the experience feels premium from the very first second, which is exactly the UX I want.

Details
Every purchaseWhatsApp Cloud APIInstant
Why It Matters

Payment clears at 11pm → the customer instantly sees "Thank you for your order! Here is what happens next…" on WhatsApp, with no one awake to send it.

The Smart Part: It Branches by What They Bought

Not every customer needs the same thing, so the workflow adapts. A few actions run for everyone, and the rest depend on whether they bought a course, booked a service, or booked a consultation. Here is exactly what fires for each:

What They BoughtRuns for EveryonePlus, Specifically for Them
A CourseWhatsApp thank-you + saved to database + Conversions APIOnboarding message for the Learn platform, and the course auto-unlocks in Moodle.
A ServiceWhatsApp thank-you + saved to database + Conversions APIA detailed intake form to collect requirements before we start.
A ConsultationWhatsApp thank-you + saved to database + Conversions APIA dedicated calendar invite to self-book a slot with me.

And I Didn't Hand-Code Any of It — Claude Did

Here is the part people find hard to believe: I am not an n8n expert, and I did not hire a developer to build this. Claude built it with me. I described what I wanted in plain English — "when a payment comes in, thank the customer on WhatsApp, save them to Supabase, and if it is a course, call the Moodle API to enrol them" — and Claude told me which nodes to use, wrote the Function-node code and the API calls, and helped me debug whenever something broke.

Whenever a node threw an error or a Moodle API response looked wrong, I pasted it back to Claude and it fixed it. So this "entire business in one workflow" isn't the work of an engineering team — it is one founder plus Claude, describing requirements and shipping them. That is the real unlock: the automation runs the business, and Claude is what let me build the automation.

Pro-Tip

Build it one branch at a time. Get the WhatsApp thank-you working end to end with Claude first, then add the database, then Moodle, then the Conversions API. Small, tested steps beat one giant workflow you can't debug.

Frequently Asked Questions

Is this really one workflow, or many?
It is one workflow triggered by a single payment event, which then branches internally based on what the customer bought. Some actions (thank-you, database, Conversions API) run for every purchase, while others (onboarding, Moodle unlock, intake form, calendar invite) run only for the relevant product type.
How does the course unlock automatically?
For course purchases, n8n calls the Moodle LMS API directly to enrol the student, so access is granted the instant payment succeeds — no manual enrolment on my side. Claude wrote the API call for me based on Moodle's documentation.
Do I need to be technical to build something like this?
No. I am not an n8n expert. I described each requirement to Claude in plain English, and it told me which nodes to use and wrote the code that goes inside the Function nodes. When something errored, I pasted it back and Claude fixed it. The build is a conversation, not a coding project.
Why send the purchase to the Conversions API?
So the ad platform learns which ads actually drive real sales. Feeding server-side purchase data to Meta via the Conversions API lets it optimize future campaigns on revenue instead of browser-limited signals, which lowers cost per result over time.
What happens if a step fails?
n8n can retry failed steps and alert me if something goes wrong, so a single hiccup (like a slow API) does not silently break the customer experience. Building and testing one branch at a time also keeps failures easy to isolate and fix.

Official Documentation & Sources

Piyush Sachdeva

By Piyush Sachdeva

Founder of Social Masla and Pulse. Author of The Growth Engine.