Premium actions vs. custom webhooks
Both achieve similar outcomes — sending data from GHL to WAGHL — but with different trade-offs:
Premium actions are faster but cost extra per execution. Custom webhooks need a few more clicks but stay free no matter how often they fire.
Premium Actions: Pre-built integration. Easier to set up, but GHL charges extra for each execution.
Custom Webhooks: Free to use. Requires manual URL and parameter configuration, but unlimited executions.
Configure a premium action
Premium actions are the easiest way to integrate WAGHL with GHL workflows.
Open a GHL workflow
In your GHL sub-account, navigate to Automation → Workflows. Open an existing workflow or create a new one.
Add the WhatsApp premium action
Click the + button to add an action. In the action picker, search for WhatsApp add-ons. Select the WAGHL premium action that matches your need.
Fill in the action parameters
Each premium action has its own configuration — message text, recipient, media URL, etc. The form-based setup means no manual URL building needed.
GHL charges extra for each premium action execution. Track your usage to avoid unexpected charges. If you're sending high volumes, the custom webhook (below) is free.
Configure a custom webhook
Custom webhooks are free but require manual setup. You'll need to know the webhook URL and the data parameters required.
Add a Webhook action in your workflow
In your GHL workflow, add a Custom Webhook action.
Enter the webhook URL
Use the webhook URL that matches your sub-account's gateway. See the webhook URL table in the Internal Notifications guide.
Enter the custom data fields
Add the parameters required for your specific use case. Each WAGHL endpoint expects different fields (message, user, media, etc.). Refer to this help center for the exact parameter names per use case.
Test before going live
Use GHL's workflow test tool to send a sample request and confirm the webhook fires correctly. Then activate the workflow.
Best practices
- Verify your API key and parameters — small typos cause silent failures
- Test once, double-check, then activate — webhook errors don't always raise visible errors in GHL
- Track premium action usage — monitor billing to avoid surprise charges
- Familiarise yourself with parameter names — bookmark the relevant help articles for quick reference
What's next?
- Send internal notifications — webhook example with full parameter list
- Missed call text back — workflow-based automation example
- All WAGHL features