Integrations
GoHighLevel and WhatsApp
Connect GoHighLevel (HighLevel) to WbizTool and your workflows send WhatsApp messages from your own WhatsApp number. Incoming WhatsApp messages can come back into HighLevel too, as a note, a tag or a task on the contact.
Everything on this page uses features that already exist on both sides: HighLevel's workflow webhooks, and the WbizTool Send message API and incoming message webhooks. You don't install anything.
Who can do it: In WbizTool, an Owner creates the API key (API keys), and an Owner or Editor sets up incoming message webhooks. In HighLevel, someone who can edit workflows in the sub-account builds them. The agency must turn on HighLevel's premium workflow features (see Before you start).
What you can do#
| Direction | Example | How |
|---|---|---|
| HighLevel → WhatsApp | A form is submitted, a tag is added or an appointment is booked, and the contact gets a WhatsApp message. | A Custom Webhook action in a HighLevel workflow calls the WbizTool Send message API. |
| WhatsApp → HighLevel | A customer messages your WhatsApp number, and the message is added as a note on their HighLevel contact. The contact is created if it doesn't exist yet. | A WbizTool inbox number posts each message to a HighLevel Inbound Webhook trigger. It needs the Unibox add-on. |
Before you start#
- A connected WhatsApp number on WhatsApp numbers, and its WhatsApp Client ID (the ID shown for the number), for example
678. - A WbizTool API key from Settings → API keys. In HighLevel it goes in an
Authorization: Bearerheader, so you don't need the Client ID. See Send the key in a header. - HighLevel's premium workflow features. HighLevel lists Custom Webhook and Inbound Webhook as premium workflow features. Agencies on any HighLevel plan can turn them on: in Agency View, go to Settings → Company and enable Workflow - Premium Features. HighLevel bills each premium run, and each sub-account gets 100 free premium runs (once, not every month). The agency can rebill this to the sub-account. HighLevel's prices are on its own help page.
- For incoming messages only: the Unibox add-on on a paid or lifetime WbizTool plan (not the free trial). It costs $20 a month or $200 a year at US list prices for each WhatsApp number in the inbox. An Owner adds it on Billing & plans (see Add-ons).
Pick a route#
The HighLevel workflow route is the shortest: HighLevel calls WbizTool directly, with no other tool in between. Use an automation tool only if your workflows already run there.
| Route | Send (HighLevel → WhatsApp) | Receive (WhatsApp → HighLevel) | Plans you need |
|---|---|---|---|
| HighLevel workflows (recommended) | Custom Webhook action → Send message API | WbizTool webhook → Inbound Webhook trigger | HighLevel premium workflow features. Receive: the Unibox add-on. |
| Zapier | LeadConnector Pipeline Stage Changed → WbizTool Send Text-Only WhatsApp Message | WbizTool Incoming WhatsApp Message → LeadConnector Add/Update Contact or Add Task | A Zapier account. Receive: the Unibox add-on. |
| Make | HighLevel Webhook action → Make Webhooks → HTTP module | WbizTool webhook → Make Webhooks → HighLevel API | A Make account. Receive: the Unibox add-on. |
| n8n | HighLevel Webhook action → n8n Webhook → WbizTool Send Message | WbizTool webhook → n8n Webhook → HighLevel node | n8n with the WbizTool community node. Receive: the Unibox add-on. |
| Pabbly Connect | HighLevel Webhook action → Pabbly webhook trigger → API (Pabbly) request | WbizTool webhook → Pabbly webhook trigger → your HighLevel step | A Pabbly Connect account. Receive: the Unibox add-on. |
Send WhatsApp messages from a HighLevel workflow#
Open or create a workflow
In your HighLevel sub-account, open Automation and create a workflow, or edit one. Give it the trigger you want, such as a form submission, a new tag or a booked appointment.
Add the Custom Webhook action
Click + where the message should go out, then Send Data → Custom Webhook (or search the actions for "webhook" and pick Custom Webhook). The plain Webhook action can't set the header and body this API needs.
Set the request
Set Event to CUSTOM and Method to POST. Set the URL to
https://wbiztool.com/api/v1/send_msg/. For Authorization, choose Bearer Token and paste your WbizTool API key, or choose no auth and add the headerAuthorizationwith the valueBearer YOUR_API_KEY. Set Content-Type toapplication/json.Paste the body
Paste one of the copy-paste blocks into Raw Body and replace
678with your WhatsApp Client ID. Use HighLevel's tag icon to add more contact fields to the message.Test and publish
Save the action and publish the workflow. Run it on a test contact with your own phone number. Each run shows in the workflow's execution logs. When WbizTool accepts the message, it answers
"status": 1. The message then goes out from your WhatsApp number.
The phone number field#
Use {{contact.phone_raw}}, not {{contact.phone}}. HighLevel's {{contact.phone}} is formatted for reading, like (515) 555-2345, without the country code. {{contact.phone_raw}} is the same number in international format, like +15155552345.
WbizTool removes the +, spaces, dashes and brackets for you. A number written with + already includes its country code, so you don't need to send country_code. If some of your contacts were saved without a country code, add "country_code": "1" (your country's calling code) to the body. It's only added to numbers written without +. See Send message → phone.
Copy-paste blocks#
URL: https://wbiztool.com/api/v1/send_msg/ · Method: POST · Headers: Authorization: Bearer YOUR_API_KEY and Content-Type: application/json
{
"whatsapp_client": 678,
"phone": "{{contact.phone_raw}}",
"msg": "Hi {{contact.first_name}}, thanks for contacting {{location.name}}. We'll reply here on WhatsApp."
}{
"whatsapp_client": 678,
"msg_type": 1,
"phone": "{{contact.phone_raw}}",
"img_url": "https://example.com/images/welcome-offer.jpg",
"msg": "Hi {{contact.first_name}}, here is your welcome offer from {{location.name}}."
}{
"whatsapp_client": 678,
"msg_type": 2,
"phone": "{{contact.phone_raw}}",
"file_url": "https://example.com/files/price-list.pdf",
"file_name": "price-list.pdf",
"msg": "Hi {{contact.first_name}}, here is our price list."
}{
"whatsapp_client": 678,
"phone": "{{contact.phone_raw}}",
"msg": "Hi {{contact.first_name}}, a reminder of your appointment with {{location.name}} at {{appointment.start_time}}.",
"expire_after_seconds": 3600
}{
"whatsapp_client": 678,
"group_name": "Sales team",
"msg": "New lead: {{contact.name}}, {{contact.phone_raw}}, {{contact.email}}"
}whatsapp_client: the ID of the number to send from. You can leave it out only when your workspace has exactly one connected number.msg: up to 3,000 characters. WhatsApp formatting works:*bold*,_italic_. For a new line, type\ninside the text. A real line break makes the JSON invalid.- Images and files: the links must be public.
msgbecomes the caption. See Sending images and files. expire_after_seconds: if the message hasn't gone out within this time, for example because the number was disconnected, it's marked expired and not sent.- Groups:
group_nameis the exact name of a WhatsApp group your number is in. Sendgroup_nameorphone, never both. See Send to group.
Log incoming WhatsApp messages in HighLevel#
This direction needs the Unibox add-on. Each message your WhatsApp number receives is posted to HighLevel's Inbound Webhook trigger. The workflow then finds or creates the contact and adds the message as a note, a tag or a task. Messages don't show up anywhere else in HighLevel.
Create a workflow with an Inbound Webhook trigger
In HighLevel, create a workflow and choose the Inbound Webhook trigger. Copy the webhook URL it shows.
Point your WhatsApp number at it
In WbizTool, open Inbox numbers. Click Add number to inbox, pick the number and paste the HighLevel URL under Webhook URL (optional). For a number that's already in the inbox, paste it in the number's Webhook settings. Under Messages to post, tick only Received messages. Each post is one premium run in HighLevel, so leave Sent messages off unless you need them.
Send a test message
From another phone, send your WhatsApp number a message. It's posted after the next check, usually within a minute or two. In HighLevel, click Test Trigger, pick the request under Mapping Reference and save the trigger. The fields are listed in Payload.
Skip groups and hidden numbers
Add an If/Else step that continues only when
eventismessage_received,contact.is_groupisfalseandcontact.phoneisn't empty. WhatsApp sometimes hides a sender's number, and group messages carry the group's ID instead of a phone number.Find or create the contact
In the Create/Update Contact action, set Phone to
+followed by contact → phone from the Inbound Webhook values. WbizTool sends the number without+, and the+tells HighLevel it includes the country code. You can also map contact → name. It's the sender's WhatsApp name, and it may replace a name you've edited in HighLevel.Add the message to the contact
Add an Add to Notes action. Write a note such as "WhatsApp message:" and pick message → content and message → timestamp from the Inbound Webhook values. You can also add Add Contact Tag (for example
whatsapp), a task or an internal notification for your team.Publish
Publish the workflow and send another test message.
| Inbound Webhook value | Use it for |
|---|---|
contact.phone | The contact's phone. Add + in front. |
contact.name | The sender's WhatsApp name. Can be empty. |
message.content | The text. For photos, voice notes and files it's a label such as 📸 Image, and captions aren't included. |
message.timestamp | When the message was sent on WhatsApp (ISO 8601, UTC). |
message.media.url | A download link for a photo or file. It expires after 3½ to 7 days, so don't rely on it in a note. |
whatsapp_phone | Which of your numbers received it, if several numbers post to the same workflow. |
event | message_received or message_sent. |
- Only new messages are posted, from the moment the webhook is set. Older chats aren't imported.
- One webhook per number. Each inbox number posts to one URL. If a Zapier Zap uses the Incoming WhatsApp Message trigger for the same number, the Zap takes the webhook over while it's on.
- Answer from HighLevel: to reply on WhatsApp from the same workflow, add the Custom Webhook action with
"phone": "{{contact.phone_raw}}". - Keep the URL private. HighLevel's Inbound Webhook doesn't check WbizTool's signature, so anyone with the URL can post to it. If it leaks, create a new trigger and paste its URL in WbizTool.
Zapier#
Zapier's HighLevel app is called LeadConnector. It has one trigger, Pipeline Stage Changed. Its actions include Add/Update Contact and Add Task. See Zapier integration for connecting WbizTool.
- Send: trigger LeadConnector Pipeline Stage Changed, then a Filter by Zapier step for the stage you want, then WbizTool Send Text-Only WhatsApp Message. Pick the number under WhatsApp Number, map the contact's phone to Phone Number and write the Message. For other HighLevel events, use the Custom Webhook action instead.
- Receive: trigger WbizTool Incoming WhatsApp Message (needs the Unibox add-on), then a Filter by Zapier step that continues only when Contact Phone Hidden and Is Group are false. Then LeadConnector Add/Update Contact with the phone set to
+and Contact Phone, then LeadConnector Add Task with Message Content.
Make#
Make's HighLevel app is called GoHighLevel. These templates use only Make's generic Webhooks, JSON and HTTP modules, so you don't need a GoHighLevel connection in Make. The receive template needs a HighLevel Private Integration token and your location ID instead (see below).
Import the blueprint
Download a template below. In Make, create a scenario, open the … menu and choose Import blueprint.
Create the webhook
Open the Webhooks module, click Add to create a webhook and copy its address.
Fill in the placeholders
Replace each placeholder in capitals in the HTTP modules, such as
YOUR_WBIZTOOL_API_KEYandYOUR_WHATSAPP_CLIENT_ID.Connect the webhook
Send: in HighLevel, add a Webhook action to your workflow with the Make address as its URL. Under Custom Data, add the key
phone_rawwith the value{{contact.phone_raw}}. Receive: paste the Make address as the number's webhook URL on Inbox numbers, with only Received messages ticked.Run it once
Click Run once in Make and trigger the workflow, or send a WhatsApp message to your number.
The receive template writes to HighLevel through its API with a Private Integration token from your sub-account's settings, with the contacts.write scope, and your sub-account's location ID. You can use the GoHighLevel app's Create a Contact and Add a Note to the Contact modules instead.
n8n#
n8n has a built-in HighLevel node. Its Contact → Create or Update operation finds a contact by phone or email, or creates one, and can add a Note. Install the WbizTool community node first: see n8n integration.
Import the workflow
Download a template below. In n8n, create a workflow and import the file (… menu → Import from File, or paste the JSON on the canvas).
Add your credentials
Open the WbizTool Send Message node and pick or create a WbizTool API credential. In the receive workflow, open the HighLevel node and pick or create a HighLevel credential.
Connect the webhook
Copy the Webhook node's production URL. Send: use it as the URL of a HighLevel Webhook action, with the Custom Data key
phone_rawset to{{contact.phone_raw}}. Receive: paste it as the number's webhook URL on Inbox numbers, with only Received messages ticked.Activate
Activate the workflow and run a test.
Pabbly Connect#
Use Pabbly Connect's own webhook trigger and its API (Pabbly) action, set up as in Send WhatsApp messages from any automation tool. For the send direction, point a HighLevel Webhook action at the Pabbly webhook URL and map phone_raw to phone. For incoming messages, paste the Pabbly webhook URL as the number's webhook URL on Inbox numbers.
Templates#
| File | What it does |
|---|---|
| ghl-blocks.md | The copy-paste blocks on this page, in one file. |
| gohighlevel-to-whatsapp.make.json | Make: HighLevel webhook → WhatsApp message. |
| whatsapp-to-gohighlevel.make.json | Make: incoming WhatsApp message → HighLevel contact and note. |
| gohighlevel-to-whatsapp.n8n.json | n8n: HighLevel webhook → WhatsApp message. |
| whatsapp-to-gohighlevel.n8n.json | n8n: incoming WhatsApp message → HighLevel contact with a note. |
The templates hold no keys. Add your own in the placeholders or credentials after importing.
Troubleshooting#
| Problem | What to do |
|---|---|
The message goes to the wrong number, or Invalid phone number | Use {{contact.phone_raw}}, not {{contact.phone}}. If the contact's number has no country code in HighLevel, add country_code to the body or fix the contact. |
Either phone or group_name parameter is required | The contact has no phone number. Add an If/Else step before the action. |
Auth Error: invalid api key | Check the Authorization header: Bearer, a space, then the key, with no quotes. The key may have been deleted. See API keys. |
Invalid whatsapp client or Invalid whatsapp client id. | Use the WhatsApp Client ID from WhatsApp numbers. It's required when you have more than one number. |
Invalid JSON format: … | The body isn't valid JSON: a missing comma, a trailing comma, a real line break in msg, or a merged value with a double quote in it. |
"status": 1, but nothing arrives | The message is queued until your WhatsApp number is connected. Check WhatsApp numbers and Message status. |
| The Custom Webhook or Inbound Webhook action is missing | The agency hasn't turned on premium workflow features (Workflow - Premium Features), or the sub-account has used its free runs and isn't rebilled. Ask your agency. |
| No incoming messages reach HighLevel | The number must show Syncing on Inbox numbers, with the right URL and Received messages ticked. The receiver must answer 2xx within 8 seconds. Requests come with the User-Agent WbizTool-Webhooks/1 (+https://wbiztool.com), in case a firewall filters by it. More in Incoming message webhooks. |
| Unibox add-on required | Incoming messages need the Unibox add-on on a paid or lifetime plan. See Plans and billing. |
| A new contact is created for every message | Map Phone with the + in front, so HighLevel matches the existing contact. |
| Group chats create odd contacts | Skip messages where contact.is_group is true in an If/Else step. |
| Incoming messages stopped after a Zap was turned on | A Zap with the WbizTool Incoming WhatsApp Message trigger takes the number's webhook over while it's on. Turn the Zap off, or use another number. |
Related#
- Send message API: every field and error
- Incoming message webhooks: inbox numbers, delivery, payload
- API keys and Client ID
- Zapier integration
- n8n integration
- Send from any automation tool: Make, Pabbly Connect and others

