How to Build a Make.com Client Onboarding Automation From Scratch

Every coach I talk to is manually onboarding clients — copy-pasting welcome emails, sending Notion links, DM-ing Zoom details by hand. Here's how to build a Make.com scenario that does all of it the moment Stripe confirms payment.

Why Make.com Instead of Zapier?

I use both at Systrify, and each has its place. But for client onboarding — where you need branching logic, multiple actions firing in a specific order, and error handling when something goes wrong — Make.com wins. Its visual canvas makes complex multi-step flows easy to build and debug without touching code.

The scenario we're building has six steps: a Stripe payment trigger, a Google Sheets row append, a personalised welcome email via Gmail, a WhatsApp message, a Notion client page creation, and a Slack ping to you so you know it fired. That's six tools, zero manual work, and it runs every time, reliably.

Building the Scenario: Step by Step

Start a new scenario in Make.com and set your trigger to Stripe → Watch Events, filtering for the event type payment_intent.succeeded. This fires the moment a client pays — not when you check your inbox, not when you remember to follow up. Immediately.

From the Stripe trigger, you get the customer's name, email, amount paid, and any metadata you've attached to the payment link (I always include a program field so the automation knows which welcome kit to send).

• Module 2 — Google Sheets: Add a Row. Map the client's name, email, payment amount, program name, and today's date into your "Active Clients" sheet. Your client roster is now always up to date without you touching it.
• Module 3 — Gmail: Send an Email. Use Make's text parser to build a personalised welcome email. Pull {{customer.name}} from the Stripe data, reference their specific program, and include their Notion onboarding page link (which you'll generate in Module 5 — use a Router if needed to handle the ordering).
• Module 4 — WhatsApp Business API: Send a Message. If you have the WhatsApp Business API connected (via 360dialog or Meta directly), fire a pre-approved template message. Something like: "Hi [Name], your spot in [Program] is confirmed. Check your email for everything you need to get started." Takes 30 seconds to set up in Make and lands in WhatsApp before your client even leaves the payment page.
• Module 5 — Notion: Create a Page. Use the Notion module to duplicate your client onboarding template page into a "Clients" database. Map the client's name as the page title, set their start date, and populate key fields. The page URL gets passed back upstream into your Gmail module — this is why Make's data flow is so powerful compared to linear tools.
• Module 6 — Slack: Send a Message. Post a simple message to your #clients Slack channel: "New client [Name] just paid for [Program]. Onboarding triggered." You always know it worked. If the Slack ping doesn't show up, something upstream broke.

The Details That Make It Actually Work

The difference between a Make.com scenario that runs for six months without issues and one that breaks in the first week is usually two things: error handling and test data.

First, turn on error handling for every module. In Make, right-click any module and add an error handler route. For a client onboarding scenario, I set it to send me a Slack DM with the full error payload if anything fails. That way I can manually fix it within minutes rather than a client silently not getting their welcome email.

Second, use real test data, not Make's sample data. Create a £1 Stripe payment link, run a real transaction, and watch every module fire. Sample data looks right but breaks in production because Stripe's actual payload has fields formatted slightly differently than the examples. Always test with live data before you activate the scenario.

One more thing: set your scenario to run on a 5-minute polling interval if you're on Make's free plan (which uses polling instead of instant webhooks). On paid plans, connect a Stripe webhook directly for true real-time triggering — no delay between payment and welcome email.

What This Actually Saves You

I built this exact scenario for a business coach who was onboarding 8–12 new clients a month. Before: she spent 25–40 minutes per client on manual welcome tasks — emails, Notion setup, WhatsApp messages. After: it's zero minutes. The scenario handles it while she's on calls, asleep, or not at her desk.

At Systrify, we build these in a single session for clients. The scenario above typically takes 60–90 minutes to build and test end-to-end. Once it's live, it runs forever. The ROI on the first month alone is a full day of time back.

If you want to extend it further, add a Router module after the Stripe trigger to branch by program type. One branch handles your 1:1 coaching program, another handles your group cohort, each with its own welcome email template and Notion page structure. That's the kind of personalisation that used to require a full operations hire.