Plug WhatsApp into your stack
Wazzap is a thin, fast layer between your WhatsApp number and the tools you already pay for. Sync HighLevel conversations, route messages through OpenAI, voice them with ElevenLabs, or branch logic in n8n. One QR pair, infinite wiring.
Overview
The Integrations section covers every native connector and webhook surface Wazzap exposes. Each integration is built to do one thing well: forward messages in real time, keep contact data in lockstep, and let your existing workflows treat WhatsApp like any other channel.
You'll find detailed setup guides for the four most common partners (HighLevel, OpenAI, ElevenLabs, n8n) plus a generic REST and webhook reference for anything custom. Most teams wire 1, 2 integrations on day one and grow from there.
New here? Start with Getting started to pair your first number, then come back to this page to wire it into your CRM or automation tool.
QR pairing vs Meta Business API
Before you pick an integration, it helps to know how Wazzap talks to WhatsApp. There are two worlds, and they have very different price tags and constraints.
- Meta Business API (official): requires a Business Solution Provider, template pre-approval for outbound, and pays Meta per conversation (24h window). Best when you need verified green tick, hundreds of thousands of OTPs per month, or strict compliance audits.
- Wazzap QR pairing: connects through the same Linked Devices flow as WhatsApp Web. No BSP, no templates, no per-conversation pricing. You keep your existing number and pay a flat monthly fee. This is what 95% of agencies and operators want.
Every integration listed below works on top of Wazzap's QR pairing. If you already run a Meta Business API number with templates approved, you can still use it inside Wazzap as a managed provider, but most teams come here precisely to skip that stack.
Per-conversation pricing from the official API can stack up fast. A mid-size agency running 30k conversations a month often pays more in Meta fees than in their entire stack combined. Wazzap is flat-rate, unlimited messages.
Integration catalog
HighLevel CRM
Native, bidirectional sync with HighLevel. Wazzap installs as a custom conversation provider
at the agency level. Map each Wazzap sub-account to a GHL sub-account once, and every
WhatsApp message lands in GHL's Conversations tab in real time. Replies sent
from GHL leave your real WhatsApp number. No Twilio, no templates, no per-conversation fees.
- Works on every GHL plan, including agency SaaS Mode.
- Supports white-label: your brand replaces "Wazzap" in the GHL conversation provider.
- Nested under it: the GPTalk Pro Assistant, our drop-in AI agent that books appointments and qualifies leads inside GHL.
Full setup guide: HighLevel CRM integration.
OpenAI
Route inbound WhatsApp messages to an OpenAI assistant (GPT-4o, GPT-5, or any model in your account) and have it reply autonomously. Pair it with HighLevel for context retrieval, or run it stand-alone for FAQ-style bots. You bring your API key, you control the prompt and the cost ceiling.
{
"trigger": "message.received",
"model": "gpt-4o",
"system_prompt": "You are a friendly support agent for Acme Co.",
"max_tokens": 400
} Detailed guide coming soon. In the meantime, ping us in Skool for a working template.
ElevenLabs
Reply with voice notes generated by ElevenLabs. The bot listens for the customer's intent, drafts a text response, then converts it to an audio note using the voice you cloned (or any preset). Customers get a 12-second voice note that sounds like a real agent. Great for warm reactivations and high-ticket follow-ups.
- Plug your ElevenLabs API key in Settings, Integrations, ElevenLabs.
- Pick a default voice per sub-account.
- Use
${VOICE}tags in templates to override per-campaign.
n8n
For anything Wazzap doesn't ship out of the box, n8n is the escape hatch. We expose a bidirectional webhook surface: inbound messages POST to your n8n endpoint, and you call Wazzap's REST API to send anything back. Build attendance bots, drip campaigns, lead routers, Slack handoffs, anything.
curl -X POST https://api.wazzap.mx/v4/messages \
-H "Authorization: Bearer $WAZZAP_KEY" \
-d '{"to": "+5215512345678", "body": "Routed from n8n"}' Webhooks and REST API
Every Wazzap sub-account can fire webhooks on the following events: message.received,
message.sent, message.delivered, message.read,
chat.opened, contact.updated, number.disconnected.
Subscribe from the dashboard or via the API.
The REST API is documented at api.wazzap.mx/v4 and ships with Node and Python
SDKs. Authentication is a bearer token scoped per sub-account, so you can hand a key to a
client without leaking the rest of your workspace.
Webhooks fire within 200ms of the underlying WhatsApp event. If your endpoint is slow, we retry with exponential backoff for up to 24 hours and surface failures in the dashboard.
Which one should I start with?
Rule of thumb based on what we see in the community:
- You sell to small businesses and use HighLevel: start with the HighLevel integration. It's the highest-leverage single setup we ship.
- You want an AI agent answering for you: layer GPTalk Pro on top of HighLevel, or plug OpenAI directly if you're not on GHL.
- You're an automation-heavy operator with custom flows: start with n8n and the REST API, then add HighLevel later if you need a polished inbox.
Whichever path you take, the underlying number stays the same. You can run HighLevel, OpenAI, ElevenLabs and n8n on a single Wazzap sub-account at once. They compose.