GHL Automations FAQ & Glossary: Every Term Explained
GoHighLevel’s automation builder uses a specific vocabulary, and confusing one term for another is the fastest way to build a workflow that doesn’t do what you intended. Below is a working glossary of the terms that come up constantly when building GHL automations, organized by function rather than alphabetically, so related concepts sit together.
The Building Blocks: Workflows, Triggers, and Actions
These three terms form the skeleton of every automation in GoHighLevel, and getting them straight matters more than any other concept on this page.
- Workflow. The container for an entire automation — everything from the trigger through every branch and action lives inside one workflow. Think of it as the flowchart itself, built visually in GHL’s drag-and-drop editor.
- Trigger. The event that starts a workflow. Common triggers include a form submission, a tag being applied, a missed call, an appointment being booked, or a pipeline stage change. A workflow can have multiple triggers, but each one independently kicks off the same automation logic.
- Action. A single step inside a workflow — send an SMS, send an email, add a tag, wait a set amount of time, create a task, add to a pipeline, or call a webhook. Workflows are built by chaining actions together in sequence.
- Condition (If/Else). A branching step that splits the workflow based on a rule — for example, “if the contact has the tag ‘VIP,’ send Email A, otherwise send Email B.” Conditions are what turn a simple linear sequence into a responsive automation.
Contact and Data Terms
Automations live or die on how well contact data is structured. These terms describe how GHL stores and references that data.
- Contact. A single record in the CRM — a lead, customer, or prospect — with associated fields, tags, notes, and history.
- Tag. A label applied to a contact, used both to trigger automations and to segment lists. Tags are the primary mechanism for tracking where a contact is in a journey without creating a separate database field for every possible state.
- Custom Field. A defined data field beyond the standard name/email/phone set — used to store business-specific information like “preferred appointment time” or “service interested in,” which automations can then reference or branch on.
- Custom Value. A reusable snippet — a business name, phone number, booking link — that gets inserted into templates and messages so the same automation can be cloned across sub-accounts or updated in one place rather than edited inside every message individually.
- Smart List. A dynamically filtered list of contacts based on criteria such as tags, custom fields, or pipeline stage. Smart Lists update automatically as contacts meet or stop meeting the filter criteria, unlike a static list that has to be manually maintained.
- Merge Field. A placeholder inside a message template (like {{contact.first_name}}) that automatically pulls the real value from a contact’s record when the message sends.
Sales and Journey Terms
These terms describe how a contact moves through a business’s sales or service process, and how automations track and respond to that movement.
- Pipeline. A visual, stage-based representation of a sales or service process — for example, New Lead, Contacted, Booked, Completed, Reactivation. Contacts (represented as opportunities) move through pipeline stages, and stage changes are one of the most common automation triggers.
- Opportunity. A specific deal or potential sale associated with a contact, tracked within a pipeline. A single contact can have multiple opportunities over time.
- Campaign. An older term still used in parts of GHL to refer to a scheduled sequence of messages, largely superseded by Workflows in the current builder but still visible in some legacy accounts and documentation.
- Funnel. A sequence of connected landing pages designed to move a visitor toward a conversion goal (booking, purchase, opt-in). Funnels are built separately from automations but frequently feed them — a funnel opt-in is a common workflow trigger.
Communication Terms
Automations exist primarily to send communication at the right moment. These terms cover the channels and mechanics involved.
- Missed Call Text Back (MCTB). A specific, widely used automation pattern where an unanswered inbound call automatically triggers an outbound SMS to the caller. Popular enough that it’s often referenced as a named feature even though it’s really just a trigger-plus-action combination.
- Conversation AI. GoHighLevel’s built-in AI chat and voice assistant, which can be configured to respond to inbound messages, qualify leads, and even book appointments autonomously within defined guardrails, distinct from a manually built workflow sequence.
- A2P 10DLC. Application-to-Person 10-Digit Long Code — the mobile carrier registration required for businesses sending SMS through automated platforms like GHL. Unregistered numbers get throttled or blocked by carriers, which is one of the most common causes of “broken” automations that are actually a compliance issue, not a workflow bug.
- Domain Authentication. The process of verifying a sending domain with SPF, DKIM, and DMARC records so automated emails don’t get flagged as spam. Required for reliable email deliverability inside any GHL automation that sends email.
Integration and Technical Terms
Automations frequently need to connect to systems outside GHL itself. These terms describe how that connection happens.
- Webhook. An automated message sent from GHL to another system (or received from another system into GHL) when a specific event occurs, used to connect automations to tools outside the native platform, like a custom booking calendar or an internal database.
- Zapier / Make Integration. Third-party automation platforms commonly connected to GHL to bridge workflows with apps that don’t have a native integration — useful, but worth using sparingly, since every external hop adds a potential point of failure a native GHL action wouldn’t have.
- Snapshot. A packaged, cloneable bundle of workflows, pipelines, funnels, and settings that can be deployed into a new sub-account in one action. The core mechanism agencies use to scale automation builds across multiple clients.
- Sub-account. An individual client or location account within an agency’s GoHighLevel structure, each with its own contacts, workflows, and settings, typically populated from a shared snapshot.
Measurement Terms
Once an automation is live, these are the terms that come up when evaluating whether it’s working.
- Enrollment. The count of contacts who have entered a given workflow, visible in the workflow’s built-in reporting, used as a baseline denominator for calculating conversion at each step.
- Goal Event. A defined outcome inside a workflow (such as booking an appointment) that GHL tracks as a completion metric, separate from simply finishing all the steps in the sequence.
- Attribution. Tracking which source, campaign, or automation is responsible for a given lead or sale, typically configured through UTM parameters and GHL’s built-in attribution reporting.
Terms That Get Confused Most Often
A few pairs of terms trip up practitioners consistently enough to call out directly. Tags versus Custom Fields is the most common: tags are best for binary or state-based flags (“has booked,” “VIP,” “cold lead”), while custom fields are best for storing actual data values (“preferred contact time: evenings”). Using a tag where a custom field belongs (or vice versa) makes automations harder to maintain and reporting harder to build.
Workflow versus Campaign is the second most common confusion, mostly because “Campaign” persists in older documentation and marketing language even though nearly all current automation building happens inside Workflows. If a tutorial or support article references a Campaign builder, it’s likely describing legacy functionality that’s been folded into Workflows in current versions of the platform.
Frequently Asked Questions
What's the difference between a trigger and an action in GoHighLevel?
A trigger is the event that starts a workflow — a form submission, a missed call, a tag being applied. An action is a step that happens inside the workflow once it's running — sending a message, waiting, updating a field, or moving a pipeline stage. Every workflow needs at least one trigger and at least one action; the trigger answers "when does this start," and actions answer "what happens next."
Are tags and pipeline stages the same thing?
No, though they're often used together. A pipeline stage represents where a contact sits in a defined sales or service process (New Lead, Booked, Completed) and is visible on a pipeline board. A tag is a more flexible label that can represent almost anything — interest, source, behavior — and isn't tied to a single visual process. Many automations use a pipeline stage change as a trigger and apply a tag as a resulting action.
What is a snapshot and why does it matter for agencies?
A snapshot is a cloneable package of an agency's entire automation setup — workflows, pipelines, funnels, and configuration — that can be deployed into a new client sub-account in one step. It's the mechanism that lets agencies scale automation delivery across many clients without rebuilding the same logic from scratch each time.
Is Conversation AI the same as a workflow automation?
No. A workflow automation follows a defined, pre-built sequence of steps in response to a trigger. Conversation AI is a generative assistant that can hold a more open-ended back-and-forth conversation, interpret intent, and take actions dynamically within configured limits. The two are often connected — a workflow might hand a conversation off to Conversation AI, or Conversation AI's outcome might trigger a workflow — but they operate on different logic.
Why do automated texts sometimes not get delivered even though the workflow shows as completed?
The most common cause is A2P 10DLC registration issues — carriers throttle or silently drop messages from unregistered or under-trust-scored numbers, and GHL's workflow log may still show the send action as "completed" because the message left the platform successfully even if the carrier didn't deliver it. Checking the number's A2P registration status is the first troubleshooting step whenever SMS delivery looks inconsistent.
What does "enrollment" mean in workflow reporting?
Enrollment refers to the total number of contacts who have entered a specific workflow, regardless of whether they completed it, dropped off partway through, or hit a goal event. It's the denominator used to calculate completion and conversion rates at each stage of the automation.
Terry has 30+ years in software and SEO. He’s the founder of Salterra Digital Services and SEO Spring Training, host of the Roundtable SEO Mastermind, and lead instructor at SEO University — teaching the exact tactics his team uses on client work.
Continue learning
Ready to master this?
This guide is one lesson from the Go High Level Automations course. Get every lesson, framework and checklist — plus the full 38-course catalog — inside SEO University.
Practitioner-focused training across the full digital marketing stack — from technical SEO to conversion optimization and the AI search era. By Salterra Digital Services, since 2011.