3 Ways to Connect WhatsApp to GoHighLevel (Costs, Limits, Which to Pick)

Every guide on this topic covers exactly one method — usually the one its author sells. Here are all three ways to get WhatsApp working with GoHighLevel, with the trade-offs stated plainly, so you can pick before you spend a week on Meta verification you might not need.

Option 1 — GHL’s native WhatsApp integration (official)

GoHighLevel offers an official WhatsApp integration built on Meta’s WhatsApp Business API. Once live, WhatsApp behaves like any other channel: messages land in the GHL inbox, workflows can send them, and conversations tie to the contact record.

What it takes:

1. A verified Facebook Business Manager — Meta’s business verification is the step that takes days and where most setups stall (mismatched legal names and unverifiable addresses are the usual culprits).
2. A phone number not registered to an existing WhatsApp app — porting a number that’s on someone’s phone means losing it there first.
3. The WhatsApp add-on enabled on the sub-account (a monthly platform fee, around the price of a takeaway), plus Meta’s per-conversation fees — a few pence/cents per 24-hour conversation window, priced by category (utility conversations cost less than marketing ones).
4. Template approval for any outbound message sent outside the 24-hour customer-service window. Meta reviews every template; write utility templates as utilities (no promo language) and they pass quickly.

Choose this when: WhatsApp is a customer-facing channel at any real volume. It’s the only option that is compliant, supported, and safe from bans.

Option 2 — GREEN API and other unofficial gateways

Services like GREEN API automate a regular WhatsApp session — you scan a QR code, and their API sends messages as if you were typing them. No Meta verification, no templates, working in fifteen minutes, and cheap.

The honesty part: this is against WhatsApp’s terms of service, and numbers do get banned — sometimes quickly, sometimes after months, always without appeal. Session drops are also real: when the linked session dies, your automation silently stops.

Choose this when: the messages are internal — order alerts to your own staff, system notifications to yourself — on a number you can afford to lose. Do not put your business’s customer channel on it.

Option 3 — bridge apps (WAGHL, TimelinesAI and friends)

A middle tier: SaaS products ($19–39/month typically) that connect WhatsApp into GHL’s conversation view for you. Some ride the official API (safe, still needs verification eventually), others wrap the unofficial session method (same ban risk as Option 2, dressed nicer). Read which one you’re buying — the pricing page rarely says it loudly.

Choose this when: you need conversations flowing this week while the Meta verification for Option 1 grinds on, or the native add-on’s per-conversation model doesn’t fit your usage. Treat it as a stepping stone, and check what happens to your message history if you later migrate.

The comparison

Automating it with n8n

Whichever transport you pick, the automation pattern is the same: an event fires (order paid, form submitted, appointment booked), n8n catches it, and a WhatsApp message goes out through GHL’s conversations API. Here’s a ready-made workflow — an order-confirmation message that upserts the customer into GHL and messages them on WhatsApp:

It uses the same Private Integration Token pattern from my n8n + GoHighLevel guide — if the Version: 2021-07-28 header is news to you, read that first.

Need the whole thing set up — verification babysitting included? That’s what I do.