GoHighLevel Automation Triggers: The Complete List + When to Use Each One
Marketing automation delivers $5.44 for every $1 spent (Amra & Elma, 2025). But that return only materializes when your trigger logic is correct. Most GoHighLevel users pick the first trigger that sounds right, then wonder why their workflows fire too often, too late, or on the wrong audience entirely.
This guide is a complete reference to every GoHighLevel workflow trigger, organized by category, with the exact scenario to use each one.
Key Takeaways - GoHighLevel offers 60+ workflow triggers across 12+ categories, from Contact Created to Shopify Order Placed. - 35-50% of sales go to the vendor that responds first, making trigger precision critical for speed-to-lead (InsideSales, 2024). - The most common automation failure we see in GHL audits is using Contact Created when Form Submitted is the correct trigger.
!Abstract technology network representing automated workflow connections
What Are GoHighLevel Workflow Triggers?
A workflow trigger in GoHighLevel is an event listener. It sits in the visual workflow builder and fires when a specific event occurs in the CRM, a funnel, or a connected integration. Triggers are not schedules. They do not wait for a calendar date. They react to real-time data changes.
The three parts of every workflow are:
- Trigger — the event that starts the workflow
- Action — what the system does after the trigger fires
- Condition — the filter that decides whether the action should run
Most users over-invest in actions and under-invest in triggers. But the trigger determines timing, audience, and context. A poorly chosen trigger creates misfires, duplicate messages, or silent failures that are harder to debug than any action misconfiguration.
35-50% of sales go to the vendor that responds first (InsideSales, 2024). That means trigger precision is not a technical detail. It is a revenue issue.
Contact Triggers: The Foundation of CRM Automation
80% of B2B companies rely on automation for lead nurturing (Expandia, 2025). In GoHighLevel, contact triggers are where most of those workflows begin. This category includes 12 triggers that react to changes in a contact record.
| Trigger | When to Use It |
|---|---|
| Contact Created | New lead routing, welcome sequences, immediate CRM alerts |
| Contact Changed | Follow-up when a key field updates (job title, company, custom value) |
| Contact Tag | Behavior-based segmentation and lane switching |
| Birthday Reminder | Relationship marketing and annual outreach |
| Custom Date Reminder | Renewal notices, contract anniversaries, seasonal campaigns |
| Contact DND | Compliance workflows when Do Not Disturb is toggled |
| Contact Engagement Score | Threshold-based re-engagement or escalation |
| Note Added / Changed | Manager alerts, coaching updates, support case tagging |
| Task Added / Completed / Reminder | Task-driven follow-up and accountability sequences |
When should you use Contact Created vs Contact Tag?
Use Contact Created for universal new-lead actions: add to a nurture sequence, notify a sales rep, or set a source field. Use Contact Tag for behavioral branching: a "Hot Lead" tag might trigger an immediate SMS, while a "Cold Lead" tag triggers a long-term drip.
When we audit GHL sub-accounts, the most common automation failure is using Contact Created instead of Form Submitted for lead-source tracking. Contact Created fires for every import, manual entry, and API push. Form Submitted fires only when a lead actually fills out a specific form. If you want attribution accuracy, Form Submitted is usually the better trigger.
Contact triggers are the starting point for 80% of B2B nurture automations, but they only work when matched to the exact business event that should start the workflow.
Lead Capture and Communication Triggers
Leads contacted within 1 minute are 7x more likely to convert than those contacted in 2 hours (HubSpot, 2024). Lead capture triggers are the engine behind that speed-to-lead advantage.
| Trigger | When to Use It |
|---|---|
| Form Submitted | The most reliable trigger for lead-source tracking and instant response |
| Facebook Lead Form Submitted | Routing Facebook ad leads into specific pipelines or sequences |
| LinkedIn Lead Form Submitted | B2B paid-social lead routing |
| TikTok Form Submitted | Short-form video campaign lead capture |
| Google Lead Form Submitted | Search and display ad lead intake |
| Customer Replied | Inbound message routing across SMS, email, and social channels |
| Email Events | Opens, clicks, bounces, unsubscribes, and spam complaints |
| Trigger Link Clicked | Interest scoring and warm-lead alerts |
| Funnel/Website PageView | Retargeting and behavioral segmentation |
| Quiz Submitted / Survey Submitted | Qualification, feedback, and segmentation |
Which lead-capture trigger is best for speed-to-lead?
Form Submitted is the cleanest choice for instant response. It fires the moment a lead hits submit, before the contact record is even fully written. That gives you the fastest possible SMS or email follow-up.
How do you avoid duplicate workflows?
Add a filter that checks whether the contact already has a specific tag or pipeline stage. If the workflow fires again on the same contact, the filter blocks the duplicate action.
Form Submitted is the trigger that enables sub-1-minute lead response, and sub-1-minute response is what produces the 7x conversion lift that separates fast responders from slow ones.
!CRM dashboard showing lead capture and pipeline management
Sales Pipeline and Opportunity Triggers
CRM automation increases sales productivity by up to 34% (Kixie, 2025). Pipeline triggers are the engine behind that lift.
| Trigger | When to Use It |
|---|---|
| Opportunity Created | New deal alerts, assignment, and initial follow-up |
| Opportunity Changed | Field updates like value, source, or expected close date |
| Opportunity Status Changed | Open, Won, Lost sequences and win/loss analysis |
| Pipeline Stage Changed | Stage-specific tasks, emails, and internal notifications |
| Stale Opportunities | Automatic revival sequences after a set period of inactivity |
Opportunity Status Changed vs Pipeline Stage Changed
Opportunity Status Changed tracks the high-level outcome: Open, Won, or Lost. Use it for win/loss emails, onboarding kickoffs, or churn surveys. Pipeline Stage Changed tracks movement within a pipeline: Prospect to Qualified to Proposal. Use it for stage-specific follow-up and task creation.
Pipeline stage changes should trigger context-aware follow-up. A prospect who just moved to "Proposal Sent" needs a different message than one who moved to "Contract Pending." The trigger makes that context automatic.
Appointment, Payment, and E-Commerce Triggers
Automated appointment reminders reduce no-shows by up to 30% (healthcare and scheduling research, 2024). Payment triggers ensure revenue events never slip through manual cracks.
| Trigger | When to Use It |
|---|---|
| Appointment Status | Booked, rescheduled, cancelled, or no-show recovery |
| Customer Booked Appointment | Direct booking confirmations and calendar invites |
| Service Booking / Rental Booking | v2 booking system automations |
| Payment Received | Buyer onboarding and thank-you sequences |
| Order Submitted / Order Form Submission | Checkout confirmation and fulfillment alerts |
| Invoice | Created, sent, due, or paid lifecycle events |
| Subscription | Create, update, pause, resume, or cancel events |
| Refund | Refund confirmation and customer-success outreach |
| Abandoned Checkout | Cart recovery emails and SMS |
| Shopify Order Placed | E-commerce fulfillment and post-purchase engagement |
| Order Fulfilled / Product Review Submitted | Shipping updates and review requests |
Which payment trigger should you use for checkout funnels?
Use Order Submitted for funnel checkouts and Order Form Submission for standalone order pages. Order Submitted confirms the payment went through. Order Form Submission fires when the form is submitted, which may include pending or failed payments depending on your processor setup.
The Appointment Status trigger powers no-show recovery, and no-show recovery is where service businesses recover the 30% of appointments that would otherwise be lost to calendar gaps.
Advanced and Niche Triggers Most Users Ignore
The Scheduler trigger and Inbound Webhook enable automations that do not require a contact record at all. That capability is essential for B2B and integration-heavy setups, yet most GHL users overlook it.
| Trigger | When to Use It |
|---|---|
| Scheduler | Time-based automations without a contact (reports, reminders, cleanup) |
| Inbound Webhook | Real-time data from external systems and custom integrations |
| Call Details | Call outcome tracking and quality monitoring |
| Transcript Generated | Missed-call recovery and conversation analysis |
| Conversation AI Trigger | AI handoff and intent-based routing |
| IVR Trigger | Phone menu-driven workflows |
| Video Tracking | Engagement scoring based on video watch percentage |
| Number Validation | Phone-quality verification and fallback logic |
| Messaging Error -- SMS | Delivery-failure alerts and channel switching |
| External Tracking Event | Server-side and client-side event capture |
Real-world use case: Inbound Webhook for ERP order sync
A retail client we work with pushes Shopify orders into an ERP. When the ERP finishes fulfillment, it sends a webhook back to GoHighLevel. The Inbound Webhook trigger catches that event and updates the contact record with a tracking number. No manual data entry. No delay.
Real-world use case: Scheduler for weekly internal reporting
An agency uses the Scheduler trigger to run a workflow every Monday at 8 AM. The workflow pulls pipeline data via a webhook, formats it into a Slack message, and posts it to the sales channel. No contact is involved. The trigger fires on time, every time.
Scheduler and webhooks enable contactless automation, which is the layer that separates basic CRM workflows from true operational systems.
Affiliate, Course, and Community Triggers
GoHighLevel now supports productized service businesses, educators, and membership communities. These triggers automate the entire student, affiliate, or member lifecycle.
| Trigger | When to Use It |
|---|---|
| Affiliate Created | New affiliate onboarding and portal access |
| New Affiliate Sales | Commission alerts and leaderboard updates |
| Affiliate Enrolled In Campaign | Campaign-specific training and resource delivery |
| Lead Created (affiliate) | Attribution tracking and affiliate nurture |
| Category Started / Completed | Course progress tracking and milestone emails |
| Lesson Started / Completed | Drip content unlocks and next-lesson nudges |
| Product Started / Completed | Course completion certificates and upsells |
| Offer Access Granted / Removed | Membership onboarding and cancellation handling |
| Product Access Granted / Removed | Product-specific access control |
| User Login | Engagement tracking and re-engagement campaigns |
| Group Access Granted / Revoked | Community membership management |
| Private Channel Access Granted / Revoked | Tiered community access |
| Community Group Member Leaderboard Level Changed | Gamification and reward workflows |
| Certificates Issued | Automatic credential delivery |
When do affiliate triggers appear?
Affiliate triggers only show up in the workflow builder if the Affiliate Manager is enabled and at least one affiliate campaign exists in the sub-account. If you do not see them, check those two settings first.
Productized businesses automate delivery via course and affiliate triggers, which turns one-time setup work into a self-running student and partner experience.
How to Choose the Right Trigger Every Time
The most common automation failure we see in GHL audits is using Contact Created when Form Submitted is the correct trigger. Here is a simple framework to avoid that mistake:
- Match the trigger to the exact business event. If the workflow should start when someone fills out a form, use Form Submitted. Not Contact Created. Not Contact Tag.
- Use filters to narrow firing conditions. A trigger without filters is a trigger that fires on everything.
- Test with sample contacts before going live. Create a test contact, force the event, and watch the workflow history.
- Document trigger logic for team clarity. Name workflows descriptively and add internal notes about why a specific trigger was chosen.
- Avoid overlapping triggers on the same event. Two workflows on Contact Created with similar filters often create duplicate messages.
If your GHL automations feel fragile or your triggers are firing inconsistently, we audit and rebuild them as part of our agency automation systems work.
Frequently Asked Questions
What is the most commonly used GoHighLevel trigger?
Form Submitted is the most commonly used trigger for lead capture workflows. Contact Created is the most common starting point for general CRM automations. The right choice depends on whether you need form-specific attribution or universal new-contact routing.
Can I use multiple triggers in one GoHighLevel workflow?
Yes. GoHighLevel allows multiple triggers in a single workflow. Be careful about overlap. If two triggers can fire on the same contact within minutes, add filters or wait steps to prevent duplicate actions.
What trigger should I use for missed call text back?
Use Call Details or Transcript Generated, depending on your phone provider setup. Call Details lets you filter by call outcome. Transcript Generated fires when a voicemail or call transcript is created, which is useful for delayed follow-up.
How do I trigger a workflow without a contact in GoHighLevel?
Use the Scheduler trigger for time-based automations that do not need a contact record. Use Inbound Webhook for external data pushes that should start a workflow without a pre-existing contact.
Why is my GoHighLevel workflow not firing?
Check five things: the workflow is published (not in draft), the trigger conditions and filters are not too restrictive, the contact meets all criteria, another workflow is not intercepting the same event, and the trigger itself is supported in your plan or sub-account configuration.
Conclusion
GoHighLevel offers more than 60 workflow triggers across 12 categories. That depth is an advantage, but only if you know which trigger matches your business event.
- Contact triggers start nurture and task-based workflows.
- Lead capture triggers power speed-to-lead and attribution.
- Pipeline triggers drive context-aware sales follow-up.
- Appointment and payment triggers protect revenue and calendar density.
- Advanced triggers like Scheduler and Inbound Webhook unlock contactless, integration-heavy automations.
- Affiliate and course triggers turn productized businesses into self-running systems.
Trigger selection is a system-design decision, not a guess. The right trigger saves hours of manual work and prevents the costly misfires that erode trust in your automation.
If your GHL automations feel fragile or your triggers are firing inconsistently, we audit and rebuild them as part of our agency automation systems work. Book a discovery call and we'll map the right triggers to your actual business events.
Turn the note into a working system.
If your account is half-configured, over-automated, or creating backend drag, TkTurners can rebuild the structure around how your team actually books, follows up, and closes.
See our GoHighLevel servicesBilal Mehmood
Co-founder
Bilal Mehmood is a TkTurners co-founder focused on AI automation, systems integration, and practical operational infrastructure for growing businesses.
Relevant service
See GHL services
Explore the service lane
