When to use this
Normally, WAGHL lists fire when a customer sends a keyword (e.g. "menu"). This article shows you how to flip the model — send the list first, before the customer types anything.
Common triggers for first-message lists:
- Lead form submitted — instant welcome menu with options
- New contact created — onboarding menu
- Tag applied — segment-specific offer menu
- Manual trigger — outbound nurture campaigns
Prerequisites
You need an existing WA List already built before you can send it as a first message. If you haven't built one yet, start with how to build a WA List.
Webhook URLs
| Provider Name | Webhook URL |
|---|---|
| WhatsApp Gateway 1 |
https://trigger1.apimerger.com/list-send
|
| WA1 Connector |
https://wa1.apimerger.com/list-send
|
| WA2 Connector |
https://wa2.apimerger.com/list-send
|
Required custom data
One key:
keyword— the keyword name of an existing WA List you've already built. The webhook fetches that list and sends it.
Setup walkthrough
Create a new workflow
In GHL: Automation → Workflows → Create Workflow.
Set your trigger
Pick whichever trigger fits your use case: Form Submitted, Contact Created, Tag Applied, etc.
Pick your action approach
Two paths — both work:
Option A: Premium Action (easier UI)
- Click WA Send List in premium actions
- Name it
- Enter the keyword of your existing list
Option B: Normal Webhook (free)
- Add a Webhook action, method POST
- URL: from the table above based on your gateway
- Custom data:
keyword= your list's exact keyword
Save & publish
Save the action, then publish the workflow.
Test it
Trigger the workflow on a test contact (e.g. submit the form yourself, or apply the tag manually). Their WhatsApp should receive the list as the first message.
Spelling matters. The keyword in this workflow must match exactly what's in your existing list. A typo breaks the lookup.
Test before going live. Always test with a real contact (your own number works) before activating for production. Bad first messages tank trust quickly.
Tips for efficiency
- Naming conventions — keep workflow names clear and consistent so you can find them later (e.g. "First Message - Onboarding", "First Message - VIP Welcome")
- Update lists regularly — first messages are high-stakes. Review them monthly to make sure pricing, options, and tone still match your business
- Document changes — keep a note of what you changed and when, so future-you can debug
What's next?
- Build a WA List — if you haven't built one yet
- Build a full chatbot — chain lists into multi-level menus
- Delete a list — when you no longer need it