GoHighLevel · ASG Help
Use ASG with GHL workflows
How to validate workflow-triggered SMS before turning on a live automation.
Before making production changes: exact screen names and platform behavior can change as GoHighLevel, Android, carriers, and the underlying messaging platform evolve. Test changes on a controlled deployment first.
Before enabling a workflow
- Make sure the connected location has passed manual inbound/outbound testing.
- Use a test contact you control.
- Confirm the workflow action uses the supported messaging path.
- Check that the contact is not opted out and has a usable mobile number.
Test one trigger at a time
Trigger the workflow once, inspect the GHL execution history, then check ASG/device activity. This makes it easier to see whether a failure occurred in GHL, the integration, the device, or the carrier.
Production tip
Add guardrails so the same contact is not repeatedly messaged by overlapping workflows.
Still not working? Contact ASG with the device name, carrier, GHL location, approximate timestamp, and the exact step that failed.