GoHighLevel Workflows: Triggers, Actions & Recipes (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 28 July 2026 · 8 min read

On this page: What workflows are · Trigger types · Action types · Six proven recipes · Testing & publishing · Naming & folder hygiene · Common mistakes · FAQ

GoHighLevel workflows are where the platform stops being a CRM and starts being an employee that never sleeps. Every automated text, appointment reminder, review request and pipeline update in a well-run sub-account traces back to a workflow someone built, tested and published. Get them right and your follow-up runs itself. Get them wrong and contacts receive three duplicate SMS messages at 2am.

I have built and audited hundreds of these across Australian and US client accounts, and the accounts that convert are always the ones with five or six boring, reliable workflows that fire every time. This guide covers how the HighLevel workflow builder works — triggers, actions, wait steps, branching — plus the six recipes I install in almost every new sub-account.

What GoHighLevel workflows are and where they live

A workflow is a sequence of automated steps that runs against a contact record. You will find them in the left menu of any sub-account under Automation > Workflows. Each workflow has two halves: one or more triggers that decide when a contact enters, and a chain of actions that decide what happens to them once they are in.

Workflows replaced the older Campaigns and standalone Triggers features years ago, and everything now lives in the single visual builder. Because workflows operate at the sub-account level, agencies typically build them once, save the sub-account as a snapshot, and push that snapshot into every new client account. That is how you install a proven automation stack in minutes rather than rebuilding from scratch.

What a workflow can touch

Inside the builder, actions can read and write nearly everything on the contact: tags, custom fields, pipeline opportunities, appointments, tasks and notes. SMS and voice route via Twilio or the built-in LeadConnector phone system, email via Mailgun or a dedicated sending domain. If you message US numbers, A2P 10DLC registration is mandatory before texts will deliver; in Australia, your consent and sender practices must line up with ACMA spam rules.

Trigger types: what enrols a contact

Triggers are the front door. A contact only enters a workflow when a trigger event fires and the contact matches the trigger's filters. You can stack multiple triggers on one workflow — any of them will enrol the contact.

Contact triggers

The workhorses: Form Submitted, Survey Submitted, Contact Created, Contact Tag (added or removed), Custom Field Changed and Birthday Reminder. Tag-based triggers are the glue of a mature account — one workflow finishes by adding a tag, and that tag silently enrols the contact into the next workflow.

Appointment triggers

Appointment Booked and Appointment Status Changed (confirmed, showed, no-show, cancelled) drive every reminder and recovery sequence. Always filter by calendar so your discovery-call reminders do not fire for a service booking. If your calendars are not set up cleanly yet, fix that first — my walkthrough on GoHighLevel calendar and booking setup covers the groundwork these triggers depend on.

Payment and pipeline triggers

Payment Received, Invoice Paid and Order Form Submission let you separate buyers from browsers the second money moves — ideal for kicking off onboarding and killing sales follow-up. On the pipeline side, Opportunity Status Changed and Pipeline Stage Changed fire when a card moves on the board, which means your sales team dragging an opportunity to "Proposal Sent" can automatically launch a five-day follow-up sequence without anyone remembering to.

Communication triggers

Customer Replied, Call Status (including missed calls) and Email Events (opened, clicked, bounced) close the loop on conversations. Call Status with the "missed" filter is the trigger behind the single highest-ROI automation in the platform, which we will get to shortly.

Action types: what happens next

Once a contact is enrolled, actions execute top to bottom. These are the ones that matter.

Messaging actions

Send SMS and Send Email support custom values like {{contact.first_name}} so every message is personalised. Keep SMS under 160 characters where you can, always identify your business, and include an opt-out path — both Twilio's A2P rules and ACMA expect it. Manual Call and Voicemail Drop round out the channel mix.

Flow-control actions

Wait steps pause the contact for a set duration, until a specific time, or until an event such as a reply. If/Else branches split the path on conditions — tag present, field value, reply received, appointment status — and turn a linear drip into genuine logic: send SMS, wait 30 minutes, branch on "replied" versus "no reply", escalate the silent branch to email and a staff task.

CRM and data actions

Add/Remove Tag, Update Custom Field, Create/Update Opportunity, Add Task and Assign User keep your CRM honest without manual data entry. The opportunity actions are underused: a lead who books should have their pipeline card moved by the workflow, not by a human on Monday morning.

AI and integration actions

Conversation AI can take over the thread and book appointments autonomously once triggered from a workflow step — I cover the full configuration in my guide to setting up GoHighLevel Conversation AI. For everything HighLevel cannot do natively, the Webhook action posts contact data to any external URL, and Google Sheets and Slack actions handle the common cases without middleware. Full action references live in the official HighLevel help centre if you need the fine print on any step.

Six proven workflow recipes

These six do the heavy lifting in nearly every account I manage. HighLevel ships pre-built recipe templates for most of them in the workflow builder's recipe library, but understanding the anatomy lets you customise properly.

1. Speed-to-lead

Trigger: Form Submitted. Actions: instant SMS ("Thanks for your enquiry, is now a good time for a quick call?"), instant email, internal notification to the sales user, wait 5 minutes, then branch — if no reply, send a booking link; if still nothing after an hour, create a call task. Leads contacted within five minutes convert dramatically better, and this workflow guarantees the five minutes.

2. Appointment reminder sequence

Trigger: Appointment Booked (filtered by calendar). Actions: immediate confirmation SMS and email, reminder email 24 hours before, reminder SMS 2 hours before with a confirm/reschedule link, and a final 15-minute nudge for virtual calls with the meeting link. Expect show rates to lift 20–30% over no reminders at all.

3. No-show recovery

Trigger: Appointment Status Changed to "no-show". Actions: wait 15 minutes (so you are not texting mid-drama), send a no-blame SMS with a one-tap rebooking link, wait a day, follow up by email, then tag noshow-unrecovered after 72 silent hours so the contact drops into long-term nurture instead of vanishing.

4. Review request

Trigger: Appointment Status "showed", tag added, or Payment Received — whatever marks a completed job in your business. Actions: wait a few hours, send an SMS with your Google review link, branch on click, and send one polite email follow-up to non-clickers three days later. Two asks maximum; more starts to feel like harassment.

5. Database reactivation

Trigger: Contact Tag reactivation-batch, applied via bulk action to a filtered smart list of cold contacts. Actions: a short, casual SMS ("We've got a couple of openings this month — still interested?"), wait for reply, and hand responders to Conversation AI or a human to book. Add contacts in batches of 50–100 per day to protect number reputation; this one regularly generates five figures from lists clients had written off.

6. Missed call text-back

Trigger: Call Status = missed. Actions: instant SMS ("Sorry we missed your call — how can we help?"), notify staff, and route any reply into your follow-up pipeline. It is the simplest workflow on this list and often the fastest payback in the whole platform; the step-by-step build is in my missed call text-back setup guide.

Testing and publishing: draft mode done properly

Every workflow has a Draft/Publish toggle at the top right of the builder. In draft mode the workflow will not enrol live contacts, but you can still run the built-in test tools. My release routine for every client build:

The pre-publish checklist

First, run the test workflow feature with a dedicated test contact — your own mobile and email on a record tagged test-contact — and confirm every SMS and email arrives and personalises properly. Second, walk each if/else branch deliberately: reply, then don't, and watch the Execution Logs to confirm each path fires. Third, check the settings: Allow Re-entry off for booking sequences, Stop on Response on for anything conversational so a human reply halts the robots. Only then flip to Published, and review the Execution Logs after the first few real enrolments — live data always finds edge cases your test contact did not.

Naming conventions and folder hygiene

An account with forty workflows named "New Workflow (copy) (copy)" is unmaintainable, and if you are an agency pushing snapshots, that mess replicates into every client account. Adopt a convention on day one and never deviate.

A convention that scales

I use [Area] - [Purpose] - [Version]: for example LEADS - Speed to Lead - v2 or REV - Google Review Request - v3. Group workflows into folders by function — Lead Nurture, Appointments, Reviews, Reactivation, Internal — and keep a "ZZ - Archive" folder for retired versions rather than deleting them, since deleted workflows take their stats and history with them. Version numbers answer "why did messaging change in March?" in seconds. For multi-account work, unlimited sub-accounts and snapshot distribution come with the agency tiers on the HighLevel pricing page.

Common mistakes to avoid

• Publishing without a test contact run. Broken custom values like a literal "{{contact.first_name}}" in a live SMS destroys trust instantly.
• Leaving re-entry on by default. A contact who submits two forms gets two parallel sequences and double the messages.
• No Stop on Response on conversational sequences. The lead replies "yes please call me" and your automation cheerfully sends message four anyway.
• Skipping A2P registration or ACMA-compliant consent. Unregistered US traffic gets filtered, and messaging Australians without consent and an opt-out invites complaints and carrier blocks.
• Ignoring time-window settings. Wait steps without time restrictions will happily deliver SMS at 3am; restrict sends to business hours.
• Building one giant workflow instead of small chained ones. Monoliths are impossible to debug — chain focused workflows together with tags instead.

If you want proven workflow recipes installed and tested in your own sub-account, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

What is the difference between a trigger and an action in GoHighLevel?

A trigger is the event that enrols a contact into a workflow, such as a form submission, missed call or pipeline stage change. Actions are the steps that then execute against that contact — sending an SMS or email, waiting, branching with if/else logic, updating tags or fields, or firing a webhook. Every workflow needs at least one trigger and one action to do anything useful.

How many workflows can I build in GoHighLevel?

There is no hard cap on workflows in a sub-account on standard HighLevel plans; you can build as many as your operation needs. The practical limit is maintainability, which is why naming conventions, folders and chaining small workflows together matter more than raw quantity.

Can GoHighLevel workflows send SMS in Australia?

Yes. SMS routes through LeadConnector or your own Twilio account using an Australian number. You do not need US A2P 10DLC registration for Australian traffic, but you must comply with ACMA spam rules: obtain consent, identify your business in the message, and provide a working opt-out such as "Reply STOP".

Do workflows run automatically once published?

Yes. Once a workflow is published, any contact who matches a trigger and its filters is enrolled automatically and moves through the actions on schedule, including wait steps and branches. In draft mode, no live contacts are enrolled, which is why you should test in draft with a test contact before publishing.

What is the fastest workflow to see ROI from?

Missed call text-back, in my experience. It is a single trigger (Call Status: missed) and one or two actions, takes under fifteen minutes to build and test, and immediately captures callers who would otherwise ring your nearest competitor. Speed-to-lead is a close second for any business running lead forms or paid ads.