GoHighLevel (GHL) workflows are the engine that makes the platform worth the subscription. Without them, GHL is an expensive CRM with a nice interface. With them, it becomes a system that follows up leads at 11pm, books appointments without human involvement, and asks for reviews without anyone remembering to do it. This guide walks through everything a UK business needs to know to set them up properly in 2026.
The guide is structured for people who have GHL set up but have not yet used workflows seriously, or who have built a few but want to understand the full range of what is possible. We cover triggers, actions, real workflow examples, and the UK-specific compliance requirements that most guides ignore entirely.
A GHL workflow is an automated sequence of actions triggered by a specific event. The trigger fires when something happens - a form is submitted, a tag is applied, an appointment is booked, a call is missed - and the workflow then runs through a series of actions: send an SMS, wait two hours, send an email, check a condition, branch into two paths based on the answer.
The underlying logic is if-this-then-that, but GHL's workflow builder lets you stack those conditions into genuinely complex sequences with branching, time delays, goal events that exit the contact from the workflow, and re-entry rules. The visual drag-and-drop builder is better than most platforms in this space.
Workflows replace the older Campaigns and Triggers system that GHL used before late 2022. If you are still using the legacy Campaigns tab, stop and move everything to Workflows. The legacy system is frozen - no new features and eventually it will be deprecated.
The trigger is everything. A poorly chosen trigger either fires the workflow for the wrong contacts or misses the contacts you actually want. Here are the main trigger types with notes on UK use cases:
Fires when a contact completes any form you specify. Use this for lead capture on your website, landing pages, or GHL funnels. If you are running Google Ads in the UK and sending traffic to a GHL funnel page, this trigger picks up every inbound enquiry the moment they hit submit.
Fires when a contact books an appointment through GHL's calendar. Set up separate workflows for new bookings versus rescheduled bookings - they need different messaging.
Fires when an appointment status changes to confirmed, cancelled, showed, no-showed, or invalid. The no-show trigger is one of the most valuable in GHL for service businesses - a contact who does not show deserves a different follow-up sequence to one who showed and bought.
One of the most flexible triggers. Because tags in GHL can be applied manually, by other workflows, by pipeline stage moves, or by webhook, this trigger connects your entire GHL system. A workflow can add a tag, which triggers a second workflow. Chain them cleanly with clear naming conventions.
Fires when a contact moves between stages in your sales pipeline. Use this to trigger internal notifications (Slack or email to your sales team) or follow-up sequences to the contact.
Fires when an inbound call to a GHL phone number is not answered. This is the trigger for the missed-call text-back workflow, which is covered in detail in the examples below.
Fires when a new contact record is created in GHL, regardless of source. Useful for internal notifications but use carefully - it fires for every contact, including ones imported in bulk.
Fires when an external system sends data to GHL via a webhook URL. This connects GHL to Stripe payment events, Calendly bookings, Typeform submissions, or any other platform with webhook output.
Sends a text message from your GHL number or a Twilio number connected to GHL. In the UK this requires a registered sender ID or a geographic number. See the compliance section below before setting up SMS actions.
Sends from your connected sending domain. GHL uses SendGrid or Mailgun under the hood. Set up proper SPF, DKIM and DMARC on your domain before running email workflows at volume.
Sends a WhatsApp message via the Meta Business API. Requires a verified WhatsApp Business account connected to GHL. In 2026 this is one of the highest-performing channels for UK leads - open rates are significantly higher than email. See the compliance section for opt-in requirements.
Pauses the workflow for a specified time (minutes, hours, days) or until a specific day and time. Use this to pace follow-up sequences and to ensure messages send at appropriate hours.
Branches the workflow based on a condition: has the contact replied to an SMS, does the contact have a specific tag, is the contact in a specific pipeline stage, has a custom field value been set. This is what separates a useful workflow from a blunt instrument.
Exits the current workflow and starts a different one. Useful for keeping individual workflows focused and manageable rather than building one enormous workflow for every scenario.
Modifies the contact's tags. Used to trigger other workflows, mark workflow completion, or update the contact's status in your segmentation system.
Writes a value to any standard or custom field on the contact record. Use this to record what workflows have fired, what stage a contact has reached, or to set values that feed into later if/else branches.
Sends a notification to a team member via email or SMS. Use this to alert sales staff when a high-value lead hits a specific stage, when a no-show needs a phone call, or when a contract is ready for review.
Sends data from GHL to an external system. Use this to create records in your CRM, trigger actions in Zapier or Make, send data to a Google Sheet, or notify a project management tool.
Goal: Move a website enquiry to a booked discovery call within 48 hours.
Goal: Reduce no-shows by 40 to 60% with automated reminders.
Goal: Re-engage contacts who missed their appointment without being aggressive.
Goal: Systematically collect Google reviews from satisfied customers without manual prompting.
Keep the review request window within 30 days of service completion. Reviews requested too long after the event are less likely to convert and may feel odd to the customer.
Goal: Respond to every missed call within 30 seconds, even outside business hours.
This workflow alone typically recovers 15 to 25% of calls that would otherwise never result in contact. It is one of the fastest-return automations in GHL.
This section is not optional reading. UK businesses running SMS and WhatsApp marketing without proper consent grounds face ICO fines and, more commonly, high complaint rates that damage sender reputation and get numbers blocked.
GDPR governs how you collect, store and use personal data (including phone numbers). PECR (Privacy and Electronic Communications Regulations) governs direct marketing by electronic means - which includes SMS and WhatsApp messages.
Under PECR, you need prior consent to send marketing SMS messages to individuals. That means an explicit opt-in - a pre-ticked box does not count. Your GHL form should have an unchecked checkbox reading something like: "I agree to receive SMS updates and marketing messages. I can opt out at any time."
Transactional messages (appointment confirmations, reminders, receipt confirmations) are not marketing and do not require the same consent level, though you still need a lawful basis under GDPR (legitimate interests usually covers transactional messages).
Meta's WhatsApp Business API has its own opt-in requirement separate from GDPR: contacts must have explicitly opted in to receive WhatsApp messages from your business. You cannot send WhatsApp messages to someone who gave you only their email or phone number without a WhatsApp-specific opt-in. Include a WhatsApp opt-in checkbox on your lead capture forms if you plan to use the channel.
Every SMS should end with "Reply STOP to opt out" or equivalent. GHL handles inbound STOP replies automatically and marks the contact as opted out. Verify this is working in your account settings before launching any sequence.
ICO guidance recommends not sending marketing messages before 8am or after 9pm. Build time restrictions into your wait steps - GHL allows you to specify "send only between 9am and 8pm on weekdays" as a workflow setting.
A GoHighLevel workflow is an automated sequence that fires when a trigger event occurs (a form submission, a missed call, a tag being applied) and then runs through a series of actions: sending SMS or emails, waiting, checking conditions, updating records, and notifying team members. It replaces manual follow-up tasks with consistent, timed automation.
Yes, provided you have proper consent. Under PECR, marketing SMS messages require explicit prior consent from the recipient - an unchecked opt-in box on your lead capture form. Transactional messages (appointment confirmations, reminders) operate under legitimate interests as a GDPR lawful basis. Always include an opt-out mechanism and honour STOP replies. Verify opt-out handling is active in your GHL account before going live.
GHL Campaigns is the legacy automation system. Workflows replaced it and offer significantly more functionality: visual drag-and-drop builder, branching if/else logic, goal events, re-entry rules, and webhook integration. GHL no longer updates the Campaigns system. If you are still using Campaigns, migrate to Workflows - the process is straightforward and worth the time.
You need a Meta Business account with a verified WhatsApp Business API connection. In GHL, go to Settings, then Integrations, then WhatsApp. You will need a UK phone number to register as your WhatsApp Business number - this number cannot also be used as a personal WhatsApp. Once connected, you can send WhatsApp messages as actions within any workflow, subject to Meta's message template requirements for the first contact.
By default, yes - GHL does not restrict sending times. You need to add a time-of-day condition manually using if/else logic or by configuring the Wait step to only advance during specified hours. For UK compliance and to protect sender reputation, do not send marketing messages before 8am or after 9pm. Transactional messages (appointment reminders for early morning slots) are more flexible but still use common sense.
A well-configured service business typically runs eight to fifteen active workflows: lead nurture (one per main lead source), appointment confirmation and reminders, no-show follow-up, review request, missed call text-back, re-engagement for cold leads, and internal notification workflows for pipeline stage changes. Start with the five examples in this guide and add complexity once those are running reliably.
We protect the real names of all clients featured in examples and case studies. Every testimonial is from a real client.
More from the blog
Work with us
Book a free 30-minute discovery call with DD and get a personalised automation roadmap.
Softomate Solutions Limited
Deen Dayal Yadav
Online
We use essential cookies to keep the site running. With your permission, we also use analytics cookies to understand how visitors use our site so we can improve it. No data is sold. Privacy Policy
