WhatsApp integrations: how to connect your store, payments and tools

WhatsApp integrations connect the tools where customers act (your store, payment provider, course platform, CRM or forms) to the place where you message them. A good integration does three things: it brings the right events across, attaches them to a person who has agreed to hear from you, and lets those events decide who gets which WhatsApp message next.

This guide explains what integrations should and should not do, the main ways businesses wire WhatsApp into their stack, where Buddy Connect fits (it is planned for late October 2026, and nothing is connectable yet), and the practical routes you can use today while you wait.

What is a WhatsApp integration?

At its simplest, a WhatsApp integration moves information between WhatsApp and another system. In practice there are two directions, and most businesses need both.

• Into your messaging platform: a purchase, a signup, a booking or a failed payment happens somewhere else, and that fact arrives in the tool you use to message customers, attached to the right contact.
• Out of your messaging platform: a reply, an opt-out or a delivery status on WhatsApp is sent back to your CRM, helpdesk or spreadsheet so the rest of the business can see it.

Under the hood, everything on the official WhatsApp Business Platform runs through Meta's Cloud API. Messages go out through the API and events such as incoming messages and delivery statuses come back as webhooks. An integration is whatever sits between those webhooks and your other tools, deciding what to store and what to send.

What should a good WhatsApp integration do?

Plenty of integrations can move data. Fewer move it in a way that keeps your number healthy and your audience trusting you. These are the tests we hold our own work to, and they are a useful checklist for any tool you evaluate.

The consent point matters most. The WhatsApp Business Messaging Policy says you may only contact people who have given you their number and "opt-in permission from the recipient confirming that they wish to receive subsequent messages or calls from you". Meta's opt-in guidance adds that the opt-in must make clear the person is agreeing to messages from your business on WhatsApp. In the UK and EU, the ICO is explicit that valid consent cannot come from pre-ticked boxes, silence or inactivity. An integration that quietly turns every customer into a WhatsApp subscriber breaks all three.

What are the ways to integrate WhatsApp with other tools?

There are four common routes. They are not mutually exclusive; many businesses use a native integration for their store and an automation tool for everything else.

Native store messaging, for example Shopify Messaging

Some commerce platforms now offer WhatsApp directly. Shopify's own help centre describes Shopify Messaging for WhatsApp, which charges per message and bills monthly, with separate rates for marketing and service messages by country. It is a reasonable choice if Shopify is your whole business. Note what that same page says about the US: you "can't send WhatsApp marketing messages to customers in" the United States, which matches Meta's own rule that marketing templates are not delivered to US numbers.

Zapier and Make

Automation platforms connect thousands of apps with triggers and actions. Zapier's WhatsApp Business app lists two triggers, "New Message Received" and "Message Status Updated", and actions including "Send Template Message", "Send Freeform Message" and "Send Media Message". That is enough to, say, send a template when a new row appears in a sheet. What it does not give you on its own is an audience with consent history, segments, an inbox or campaign reporting; you build those rules yourself, step by step.

Direct API work

If you have developers, you can call Meta's Cloud API directly or use a platform API on top of it. This is the most flexible route and the most work: you handle template approval, the 24-hour window, webhook signature checks, retries and opt-outs. We cover the trade-offs in our WhatsApp Business API integration guide.

What is Buddy Connect?

Buddy Connect is the integration layer we are building into Buddy. Its job is to bring customer activity from the tools you already use into the same loop that powers the Buddy App: opt-in, audience, WhatsNews, inbox, automations and insights. Purchases, payments, enrolments and signups become context on a subscriber, so the next message can respond to what that person actually did.

It is not live yet. The first release is planned for late October 2026, shortly after Buddy 1.0 launches on 12 October. Here is what that first set is planned to cover.

We will only mark an integration as available when it works end to end. Until then, each integration's page (start from the integrations overview) says it is in development, and the call to action is a waitlist rather than a connect button.

How will Buddy Connect work?

Every connector follows the same three steps. The idea is that connecting a new tool should feel the same whether it is a store, a payment provider or a form builder.

1. 1Authorise. Connect the external tool and choose the Buddy workspace it should send activity to. You decide which account and which permissions.
2. 2Map. Choose which events and fields should become subscriber context: for example order placed, product purchased, payment failed, or a course enrolment. You also decide how opt-in state is carried across, so a buyer is not treated as a subscriber unless they agreed.
3. 3Use. Those signals then feed audiences, automations, WhatsNews targeting and reporting. A new buyer can land in a product audience; a revenue figure can finally appear next to the campaign that preceded it.

A fourth step runs in the background: monitoring. We plan to show sync status, permissions and failed events for each connection, so you can trust what the integration is doing without guessing.

What will connected data make possible?

The point of connecting tools is better messages, not more of them. Some examples of what we are designing for, clearly labelled as planned:

For store-specific journeys (post-purchase, restocks, win-back), this is also the foundation of Buddy eCommerce, which depends on these connectors and is coming soon. Our guide to WhatsApp for ecommerce covers the plays in detail, including which ones you can run today.

How can you connect your tools to WhatsApp today?

You do not need to wait for late October to get customer data into Buddy. Four routes work right now, and each keeps consent intact.

1. Import a CSV of people who already agreed

In Audience you can paste numbers or upload a CSV with name and phone columns. Only import people who have actually opted in to WhatsApp messages from you, then add tags (for example bought-candles or course-2026) so you can target them later. Buddy normalises numbers to international format. You can also export your audience as a CSV whenever you like.

2. Collect opt-ins at the source with your page and QR code

Every workspace has a hosted opt-in page at usebuddy.app/yourname, with a QR code and a copyable link. Put the link on your order confirmation page, in your receipt emails, on a thank-you screen after payment, or print the QR on packaging. Each opt-in is recorded with its date and source. Our WhatsApp opt-in guide has sample wording that makes clear what people are signing up for.

3. Embed the opt-in form on your site

Buddy Embed (in beta) adds a small opt-in form with a name field, WhatsApp number, consent checkbox and Subscribe button to any website with one line:

<script src="https://usebuddy.app/api/embed/YOUR-HANDLE"></script>

Because embed signups use the same path as the opt-in page, they fire your "When someone subscribes" automations. That means a welcome message can go out automatically. Use an approved template for it: the person has not messaged you yet, so the 24-hour customer service window is not open. More in our guide to the WhatsApp opt-in widget.

4. Push subscribers from your own systems with the API

The Buddy API is in early access, and the Subscribers endpoints are live today. Create a key in Settings, API keys (it is shown once and stored hashed), then add a subscriber from your checkout, CRM or backend when someone opts in there:

curl -X POST https://usebuddy.app/api/v1/subscribers \
  -H "Authorization: Bearer bd_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{"name": "Amara", "phone": "+447700900123", "tags": ["bought-candles"]}'

A GET to the same endpoint lists your subscribers. Contacts, sending approved templates, campaigns and signed outbound webhooks are planned for the API's public beta from 12 October 2026. See the Buddy API page for what is live.

Putting it together: a worked example without an integration

Imagine a candle shop in Leeds selling on Shopify. Until Connect ships, it adds its Buddy opt-in link to the order status page with the line "Get restock alerts and care tips on WhatsApp". New subscribers get a welcome template automatically. Once a month it exports its recent Shopify buyers, checks them against its Buddy audience, tags the ones who subscribed as recent-buyer, and schedules a WhatsNew to that tag. It is more manual than an integration, but consent is clean and every message goes to people who asked for it.

How do you choose the right WhatsApp integration?

Ask these questions of any option, including ours:

1. 1Where does consent come from? If the answer is "everyone with a phone number", walk away.
2. 2Which template category does each event use? Order and delivery updates can be utility; anything promotional is marketing, per Meta's categorisation guidance.
3. 3What happens on STOP? Opt-outs should flow back to every connected tool.
4. 4Can you see failures? You need a log, not faith.
5. 5Who owns the WhatsApp account? With Buddy, your number, templates and account stay in your own Meta business portfolio, and Meta bills its message fees to you directly.
6. 6Will it work for your markets? Marketing templates do not reach US numbers, and WhatsApp limits how many marketing messages each person receives from all businesses. Plan journeys that still make sense under those limits.

For a wider view of how a WhatsApp platform should handle audience, templates, sending and reporting, read our pillar guide to choosing a WhatsApp marketing platform.

Frequently asked questions