When a new customer is created in Pabbly Subscription Billing, send welcome message to user's WhatsApp using WA.Team

When a new customer is created in Pabbly Subscription Billing, FlowMattic sends them a WhatsApp welcome through WA.Team, using an approved template message you pick.

Pabbly Subscriptions

WhatsApp by WA.Team

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 534 sites Free to import

What this workflow does

A new subscriber has just handed over their details, and a short hello on WhatsApp is a personal way to confirm you've got them. This workflow sends that welcome automatically, so it doesn't depend on someone watching the billing dashboard.

The Pabbly Subscriptions trigger fires when a customer is created in Pabbly Subscription Billing. The customer record, including the contact details you collect at signup, is passed to the next step.

The second step uses WhatsApp by WA.Team to send a template message. WhatsApp only lets businesses open a conversation with a pre-approved template, which is why this flow uses one rather than free text: it can reach a customer who has never written to you. The step ships unmapped, so after import you connect WA.Team, choose your welcome template, and map the customer's phone number and any template variables, such as the first name.

Every new customer record starts a run, so make sure your Pabbly checkout collects a phone number with the country code. Create a test customer and look at Task History to see the phone field Pabbly sends and the reply WA.Team returns.

Welcome note for a new SaaS subscriber

A software company that bills through Pabbly greets each new customer on WhatsApp with a template that links to the getting-started guide.

Membership sign-up confirmation

A paid community sends new members a WhatsApp template naming the group and saying where to find the first session details.

Support contact saved on the customer's phone

A service business uses the welcome template to introduce its WhatsApp number, so new customers have it on hand when they need help.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Pabbly Subscriptions Customer Create
Fires when a customer is created in Pabbly Subscription Billing. The new customer's details, such as name, email and phone, are handed to the WhatsApp step.
Step 2Action
WhatsApp by WA.Team Send Template Message
Sends an approved WhatsApp template through WA.Team. Nothing is mapped yet: after import, connect WA.Team, pick the welcome template and map the customer's phone number and the template's variables.

What you need

FlowMatticCore
Pabbly Subscriptions AccountAccount
WhatsApp by WA.Team AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Have your welcome template approved for your WhatsApp business number before you import, so it is ready to choose in the Send Template Message step.
Collect the phone number on your Pabbly checkout with the country code included, since WhatsApp needs the full international number.
Add a Delay between the Pabbly trigger and the WA.Team step if you'd rather the welcome arrive a few minutes after signup instead of instantly.
Put a Filter between the trigger and the WA.Team step that continues only when the phone number is not empty, so customers who left it blank never reach WA.Team.

Questions about this workflow

Why is the Pabbly welcome sent as a WA.Team template rather than free text?

WhatsApp only delivers free-form messages within 24 hours of the person messaging your business. A brand-new Pabbly customer usually hasn't, so an approved template is the way to start that conversation.

Which Pabbly field supplies the number the welcome goes to?

From the Pabbly Subscription Billing customer record. You map that phone field into the WA.Team step after import. Check a test run to see the format Pabbly stores it in.

Can the WA.Team welcome include the customer's first name?

Yes, if your WhatsApp template has a variable for it. Map the name field from the Pabbly customer into that variable in the Send Template Message step.

Does an existing Pabbly customer who buys a second plan get another welcome?

The trigger fires when a customer is created, not on each purchase. A second subscription for an existing customer record shouldn't start a new run; confirm with a test in your Pabbly account.