GoHighLevel workflow automation lets you build if-this-then-that sequences inside a sub-account: a trigger such as a form submission, a booked appointment or a pipeline stage change starts the workflow, and actions such as SMS, email, waits, tags, opportunity updates, internal notifications and webhooks run in order. Most agency value comes from a handful of reliable workflows, such as speed to lead, appointment reminders, no-show recovery and review requests, built cleanly and tested properly.
I have built and fixed a lot of GHL automation for marketing agencies. This guide is the practical version: how the builder works, how to structure workflows, and what to watch out for.
How GoHighLevel workflow automation works in the builder
Workflows live under the Automation section of each sub-account. A workflow has three parts:
- Triggers: one or more events that enroll a contact, each with optional filters
- Actions: the steps that run for each enrolled contact, top to bottom
- Settings: rules for re-entry, sending windows, stop on response and similar behaviour
You can start from a blank workflow or from one of the prebuilt recipes HighLevel provides. Recipes are a decent way to see how a pattern is meant to work, but I usually rebuild them to match the client's naming and fields.
GoHighLevel workflows: triggers
Triggers decide who enters a workflow. Common ones agencies use:
- Form Submitted or Survey Submitted
- Contact Created or Contact Tag added
- Customer Booked Appointment or Appointment Status changed
- Pipeline Stage Changed or Opportunity Status Changed
- Customer Replied
- Call Status, for missed calls
- Payment Received or invoice events
- Inbound Webhook, for data coming from outside GHL
Each trigger can take filters, such as a specific form, calendar, pipeline or tag. Always add filters. A Contact Tag trigger without a tag filter fires on every tag. I cover the full list in GoHighLevel workflow triggers.
Actions
Actions are what the workflow does. The ones I use most:
- Communication: send SMS, send email, voicemail drop, internal notification
- Timing: wait for a set time, wait until an event, or wait until a condition
- Logic: if/else branches, goal events, go to another step
- Contact updates: add or remove tags, update fields, assign to a user, change DND settings
- Opportunities: create or update an opportunity, move pipeline stage
- Workflow control: add to another workflow, remove from a workflow
- External: webhook or custom webhook to send data to Make, n8n or another system
Some triggers and actions are premium features billed per execution, and AI actions are often priced separately. Check HighLevel's current pricing and help docs before you design a high-volume workflow around them.
Workflow settings that matter
- Allow re-entry: whether a contact can enter the same workflow more than once. Off by default in many cases. Turn it on for workflows like appointment reminders that should run each time.
- Time window: restricts when messages send, so leads do not get texts at 2am.
- Stop on response: ends the workflow when the contact replies, which is essential for nurture sequences.
- Sender details: the from name, email and number used for messages.
Most "my workflow did something weird" issues I debug come back to one of these settings.
The core workflows every agency should build
1. Speed to lead
Trigger on form submission or lead ad. Send an immediate SMS and email, notify the assigned user, create an opportunity in the first pipeline stage, and start a short follow-up sequence that stops on reply. I explain the logic in speed to lead automation.
2. Missed call text back
Trigger on call status for missed inbound calls. Send a short SMS so the caller is not left with voicemail, and notify the team. See GoHighLevel missed call text back.
3. Appointment confirmation and reminders
Trigger on appointment booked. Send a confirmation, then reminders before the appointment using waits relative to the appointment time.
4. No-show recovery
Trigger on appointment status changing to no-show. Send a friendly rebook message with the calendar link and create a task for the rep.
5. Review requests
Trigger on a pipeline stage such as Job completed, or on a tag. Send a review request with the review link, then one reminder.
6. Pipeline hygiene
Trigger on stale opportunities or stage changes. Notify the owner when deals sit too long, and move lost deals into a reactivation workflow.
A GoHighLevel automation tutorial: building speed to lead
Here is the order I build a speed-to-lead workflow in:
- Create the workflow and name it clearly, such as "Lead: Website form, speed to lead v2".
- Add the Form Submitted trigger with a filter for the specific form.
- Add Create or Update Opportunity, set to the first stage of the sales pipeline.
- Add Assign to User if the account uses round robin.
- Send SMS: short, personal, one question or a booking link.
- Send Email: confirmation with more detail.
- Internal Notification to the assigned user with lead details.
- Wait a set period, then an If/Else checking whether the contact has replied or booked.
- If not, send a follow-up SMS. Repeat once or twice with longer waits.
- In settings, turn on stop on response and set the sending time window.
- Publish, then test with your own contact details.
Texting in the US requires proper consent and A2P 10DLC registration. Get registration sorted before going live.
Naming and organizing workflows
Agencies with many sub-accounts need a convention. I use:
- A prefix for the area: Lead, Appt, Pipeline, Review, Billing, Internal
- The trigger source
- A version number
Group workflows into folders by area. Delete or archive old versions so nobody edits the wrong one. If you deploy the same workflows to many clients, build them once and distribute them with snapshots.
Testing workflows properly
- Use a test contact with your own phone and email.
- Use the test feature in the builder where available, but also run a real end-to-end test through the actual form or calendar.
- Check the execution logs for each contact to see which step ran and why it stopped.
- Shorten waits temporarily while testing, then restore them before publishing.
- Test the stop conditions: reply, book, opt out.
When to go outside GoHighLevel
GHL workflows are excellent for contact-level communication. They are less suited to agency-level operations that span many sub-accounts or other tools, such as posting client wins to Slack, creating ClickUp tasks, or building reports. For those I send data out with a webhook action to Make.
How I build this
I build and repair GoHighLevel workflows for agencies, and connect GHL to Slack, ClickUp and Google Sheets in Make for the operations side. If your workflows misfire or double-send, Automation Rescue is a 48-hour fix. For cross-tool alerts and reporting, see the Agency Reporting and Alerts Pack. Or start with a free teardown.
FAQ
What is a GoHighLevel workflow?
A GoHighLevel workflow is an automation inside a sub-account that enrolls contacts when a trigger fires, such as a form submission or appointment booking, and then runs a sequence of actions like SMS, email, waits, tags and pipeline updates.
How do I create a workflow in GoHighLevel?
Go to the Automation section of the sub-account, create a new workflow from scratch or a recipe, add a trigger with filters, add your actions in order, review the settings, then publish and test with your own contact.
Why is my GoHighLevel workflow not sending messages?
Common causes are a trigger without the right filter, re-entry being off, a sending time window, the contact being on DND, or SMS registration issues. Check the contact's execution log to see where it stopped.
Can GoHighLevel workflows connect to other tools?
Yes. Workflows can send data out through webhook actions and receive it through an inbound webhook trigger, which lets you connect GHL to tools like Make, n8n, Slack and Google Sheets.