Send a WhatsApp message from any GHL workflow with one Custom Webhook step. The message is logged in the contact's GHL conversation and goes out through your WA MSG channel — here's the whole setup, start to finish:
Add a Custom Webhook action, set the method to POST with your webhook URL, add your fields as Custom Data, and save — that's the whole setup.
Find your webhook URL
The webhook URL depends on which WAGHL gateway your sub-account is using.
Open your GHL sub-account
Switch to the GHL sub-account you want to send from.
Check your provider name
In GHL, go to Settings → Phone Numbers → Advanced Settings and note the Provider Name shown there.
Match it to the webhook URL
Use the table below to find the right webhook URL for your gateway. The request method is POST.
| Provider Name | Webhook URL |
|---|---|
| WhatsApp Gateway |
https://trigger.apimerger.com/webhook
|
| WhatsApp Gateway 1 |
https://trigger1.apimerger.com/webhook
|
| WA1 Connector |
https://wa1.apimerger.com/webhook
|
| WA2 Connector |
https://wa2.apimerger.com/webhook
|
Add it to a workflow
Add a Custom Webhook action
Open Automation → Workflows, open or create a workflow, and add a Custom Webhook action where you want the message to send. Paste the webhook URL from above and set the method to POST.
Add the Custom Data fields
Fill in the fields below. You can use GHL merge fields such as {{contact.phone}} and {{contact.first_name}} in any value.
Test, then activate
Use GHL's test tool to send a sample, confirm the message shows in the conversation and arrives on WhatsApp, then turn the workflow on.
Request fields
Send these as Custom Data on the webhook step. Everything here is optional — by default the message goes to the contact in the conversation, from an automatically chosen number.
| Field | Required | What it is |
|---|---|---|
message |
Required* | The text to send. Supports merge fields. *Either message or a media URL must be present. |
number |
Optional | Who to send to, with country code and no + — e.g. 15672346789. Leave it blank to send to the contact in the conversation. Enter a number to send somewhere specific instead (handy for internal alerts to a team member), or several numbers separated by commas. |
media_url |
Optional | A public https link to an image, video, or document to send. When you include media, message is used as the caption. url is also accepted as the field name. |
sender_number |
Optional | Which of your connected numbers sends the message. Leave it out to let GHL choose the sending number automatically (see below). |
You no longer need a separate media endpoint. Add media_url to the same webhook to send an attachment, with message as the caption.
Which number sends it
The sender_number field is optional, and how it behaves is simple:
- If you set
sender_number— the message sends from that number. It must be one of your numbers that is connected and active; if it isn't, the message won't go out. - If you leave it blank — GHL picks the sending number the same way it does for a message you send by hand from the conversation: the contact's number tag, the assigned user's number, a
{wa#…}override, or your default number. WAGHL never picks a number at random.
Worked examples
Reply to the contact — leave number out and the message goes to the contact in the conversation:
message: Hi {{contact.first_name}}! Thanks for reaching out — how can we help?
Notify a specific person — set number to send an internal alert to a team member instead of the contact:
number: 15672346789
message: New lead: {{contact.first_name}} {{contact.last_name}} — {{contact.phone}}
Send an image — add media_url, with message as the caption:
media_url: https://yoursite.com/welcome.jpg
message: Welcome aboard, {{contact.first_name}}! 🎉
What's next?
- WhatsApp as a separate channel — set a number up as a WA MSG channel
- Premium actions & webhook — the difference between premium actions and free webhooks
- Connect multiple numbers — add more sending numbers