I built a connected GoHighLevel workflow system that manages the complete Life Agent webinar lifecycle — from invitation and registration through attendance detection, coach assignment, no-show recovery, and long-term nurture.
Instead of treating registration, attendance and follow-up as separate processes, the system uses tags, opportunity stages, trigger links and workflow handoffs to move each contact through the correct state.
A webinar funnel has multiple states. Someone can be invited, register, attend, miss the event, or require a different follow-up depending on who owns the contact.
The automation needed to keep those states synchronized without relying on manual movement between workflows.
Each workflow has one primary responsibility, while tags and pipeline stages create the handoffs between them.
A long-term invitation sequence designed to move Life Agents toward webinar registration.
The central workflow. Handles registration, CRM updates, round-robin ownership, confirmations and event reminders.
A lightweight state-change workflow that detects the webinar trigger-link click and updates the contact.
Re-engages contacts who registered but did not attend the webinar through a long-term nurture sequence.
The real power of the system isn't the number of emails. It's the way contact state changes are used to control what happens next.
Once registered, the contact is placed into a timed reminder sequence around the selected Tuesday or Thursday webinar.
When a registered contact still has the Registrant state after the post-event check, the system marks the contact as missed, updates the opportunity, and hands the contact to the RNS workflow.
Form submission starts the registration lifecycle while a specific trigger-link click supplies the attendance signal.
Contact tags are used as explicit state indicators so the system can distinguish registered, attended and missed contacts.
Opportunity stages mirror the contact's lifecycle inside the Life Agents pipeline.
Registered contacts are equally assigned to Bill or Rick, allowing later branches to send the correct coach-specific follow-up.
The real objective was to build a system where every meaningful contact action changes their state — and that state determines what happens next.