CRM Enrolled - GHL
Last updated: April 12, 2026
Last Updated: April 12, 2026
Customer-Facing Guide
What this trigger means
CRM Enrolled - GHL is used when a Sendblue workflow should begin because a contact was enrolled from the GoHighLevel side.
When to use it
When your workflow starts from a GoHighLevel enrollment event.
When Sendblue behavior should follow from a CRM-side workflow decision in GHL.
What to make sure is true first
The GHL integration is connected properly.
The contact actually qualifies for the GHL workflow/enrollment you expect.
The Sendblue-side workflow logic is prepared for the data that GHL passes through.
Common mistakes
Assuming the contact enrolled in GHL when the trigger conditions were never met.
Troubleshooting Sendblue delivery before confirming the enrollment reached Sendblue at all.
Forgetting that missing fields or wrong mappings can break later workflow steps even if enrollment itself happened.
How to verify it worked
Check whether the contact was enrolled on the GHL side.
Confirm Sendblue shows the workflow enrollment/history you expected.
If nothing reached Sendblue, troubleshoot the CRM trigger path first.