Connect WhatsApp for notices and campaigns

Connect your WhatsApp Business number in one click (keeping your app and chats) or manually with Meta Cloud API or Twilio, and start sending from Xtarly.

WhatsApp in Xtarly uses your own WhatsApp Business number: messages go out under your business name, not ours. There are two ways to connect it:

One-click connection (recommended) — you authorize from a Meta window and confirm on your phone. You keep your number, your chats and your WhatsApp Business app.
Manual connection (advanced) — for businesses that already have their own Meta app, or use Twilio.

Everything happens in WhatsApp → Connection tab.

Prerequisite: WhatsApp must be available on your plan. It's included in Shared, Branded and Premium, and on Wallet it can be added as a paid add-on (+$5 USD/mo or +$99 MXN/mo, depending on your account's currency). On Wallet, if it's not active, the panel shows a button to activate it; before checkout you confirm that you already have (or know how to get) your Meta or Twilio account.

Option A — One-click connection (recommended)

It's the first thing you see in the Connection tab. Click Connect my WhatsApp Business: a Meta window opens where you pick your business and your number, and the confirmation happens on your own phone — Meta sends you a WhatsApp message. You never have to copy a token or paste a URL.

What you keep and what changes

✅ You don't change numbers or lose your chats. You keep replying from your WhatsApp Business app as always.
✅ Both sides stay in sync: what you write from your phone shows up in Xtarly's conversations, and what you send from Xtarly reaches your phone.
✅ Your history can come along: if you agree to share it from your app, Meta delivers your conversations from up to 180 days back one single time, and they appear in the panel.
⚠️ Your WhatsApp Web sessions are closed and you'll have to link them again.
⚠️ Broadcast lists, disappearing messages and live location are turned off.
⚠️ Meta bills the conversations to you, with your own payment method.

Below the button there's a secondary option: "I don't use WhatsApp Business: register a new number". That path registers a dedicated cloud number and takes the number out of the WhatsApp Business app, so only use it if you don't reply from your phone.

What Xtarly does when you finish

Without you touching anything else, it:

validates against Meta that the number responds, and shows its quality rating and your messaging tier;
sets up receiving inbound messages and delivery statuses (the webhook and its token are generated for you);
imports the templates that already lived in that WhatsApp account, with their real status.

If part of the setup didn't complete, the screen tells you right then instead of letting you find out when a send fails.

Option B — Manual connection (advanced)

In the same tab, further down, there's Manual connection (advanced), collapsed: open it with the chevron. Use it only if you already have your own Meta app or you work with Twilio. Pick one of the two providers.

Meta Cloud API

Create an app in Meta for Developers

Go to developers.facebook.com → My Apps → Create App → type Business.

Add the WhatsApp product

Inside your app, add the WhatsApp product. In WhatsApp → API Setup you'll see two values to copy:

Phone Number ID — your number's identifier.
WhatsApp Business Account ID (WABA ID) — the business account.

There you also register and verify your business phone number.

Generate a permanent token (System User Access Token)

The token Meta shows in "API Setup" is temporary (lasts 24h). For production you need a permanent one:

Go to Business Settings → Users → System Users.
Create a System User (Admin role).
Generate a token with the whatsapp_business_messaging and whatsapp_business_management permissions.
Copy that token (starts with EAAB...).

Connect it in Xtarly

In WhatsApp → Connection → Manual connection (advanced), choose the Meta Cloud API provider and fill in:

System User Access Token — the EAAB... token.
Phone Number ID — from Step 2.
WhatsApp Business Account ID — from Step 2.

Click Connect and validate.

Set up the webhook (recommended)

The webhook lets you receive delivery statuses and inbound messages (for the conversations Inbox).

In Xtarly (same tab) make up a text for the Webhook Verify Token (any string, e.g. xtarly-my-business-2026) and enter it in that field.
From Meta → App Settings → Basic, copy the App Secret and paste it into Xtarly's App Secret field. Save.
In Xtarly, copy the webhook URL shown (ends in /api/webhooks/whatsapp/meta/...).
In Meta → WhatsApp → Configuration → Webhooks, paste that URL, paste the same Verify Token from point 1, and subscribe to the messages field.

Test the connection

Click Test connection. Xtarly queries Meta and shows your number's quality (green/yellow/red) and your messaging tier. If it's green, you can send.

Twilio

Copy your Twilio credentials

In the Twilio console home page, copy:

Account SID — starts with AC....
Auth Token — the authentication token.

Identify your sender number

Note your WhatsApp number in international format, with the country code. For example: +5213321017080. (Twilio's Sandbox number works for testing.)

Connect it in Xtarly

In the manual connection, choose the Twilio provider and fill in:

Account SID — the AC....
Auth Token — your token.
WhatsApp number — just the number, e.g. +5213321017080 (from Step 2).

Click Connect and validate.

Set up the webhook

In Xtarly copy the webhook URL (ends in /api/webhooks/whatsapp/twilio/...) and paste it into the messaging configuration of your WhatsApp sender in Twilio. Twilio verifies the signature automatically with your Auth Token, so there's no extra secret to paste.

Test the connection

Click Test connection in Xtarly to confirm the credentials work.

Your credentials are encrypted at rest and never shown back to you: the panel only displays the last 4 characters.

What you see once it's connected

The Connection tab stops asking for data and shows the number's card:

Field	What it's for
Provider and status	Meta Cloud API or Twilio, labeled Active or Invalid.
Phone number ID and WhatsApp account (WABA)	Which number you're connected with, not just that a connection exists. On Twilio, the sender number.
Credential	The last 4 characters, so you can tell one account from another.
Quality	Meta's rating: green, yellow or red.
Messaging tier	How many new conversations you can start per day.

Right there you also get Test connection (asks Meta again) and Disconnect. The webhook URL card only shows up if you connected manually: one-click connections don't need it, because Xtarly already subscribed the account when the setup finished.

If you switch accounts or numbers

Template approvals live in the WhatsApp account (WABA), not in Xtarly. That means:

When you connect a different account, templates that were approved go back to draft and must be resubmitted for review. The panel tells you how many, so you don't find out when a send fails.
Templates that already existed in the account you connect are imported with their real status, and if you go back to the original account they recover their approval without resubmitting.

Troubleshooting

Problem	Likely cause	Fix
The one-click button is stuck on "Loading…"	An ad blocker or privacy extension is blocking Meta's connector	Disable it for this site and reload the page.
You connected, but no messages come in	The number was connected without activating reception (the screen warns you when you finish)	Register it from WhatsApp Manager, or connect again.
Your templates show as drafts	You connected a different WhatsApp account and approvals don't travel with it	Resubmit them for review from the Templates tab.
Token stops working after 24h	You used the temporary "API Setup" token in the manual connection	Generate a permanent System User Access Token (Option B · Step 3).
"Number not registered"	The number didn't finish registration in Meta	Finish the number registration/verification in WhatsApp → API Setup.
Your automated alerts pause on their own, saying WhatsApp can't charge them	Your WhatsApp Business account in Meta has no currency or payment method set (error 131042). It isn't an Xtarly failure, and while it lasts no alert goes out	Set it up at `business.facebook.com/billing_hub`, then use Check status with Meta in the Automated alerts tab: it switches back on every alert that had been stopped by billing.
Quality is yellow or red	Too many user blocks/reports	Send only to people who opted in, with useful templates; quality recovers over time.
Can't send campaigns	Templates aren't approved	Create templates in the Templates tab and wait for Meta's approval.

Already connected? The next step is automated WhatsApp alerts to your customers: 11 ready-made messages that go out on their own when a customer earns a stamp, completes their card or has a birthday.

Connect WhatsApp for notices and campaigns

On this page