Guides

GoHighLevel Automations: 7 Workflow Recipes to Copy

Copy-ready GoHighLevel workflow recipes for new leads, missed calls, reminders, no-shows, reviews, stale deals and old leads, with the settings that stop double texts.

By OmniFlow Editorial Team10 min read

A row of connected workflow cards starting from one trigger card and branching into message steps

GoHighLevel automations are workflows: a trigger, such as a form being submitted or an appointment being booked, starts a run, and the actions after it send texts and emails, update the pipeline, wait, and notify your team without anyone touching it. You build them in the Workflows area of the Automation section in each sub-account (HighLevel, 2025).

Below are seven recipes with the trigger, the waits, the actions and the exact message, the order to build them in, and the settings that stop double texts. If you are still deciding whether the platform suits you, start with what GoHighLevel is and what it replaces. Every menu and setting name below was checked in HighLevel’s help centre on October 27, 2026.

What are GoHighLevel automations?

An automation in GoHighLevel is a workflow with three kinds of steps. The trigger is the event that starts it, such as Form Submitted, Customer Booked Appointment, Appointment Status or Stale Opportunities (HighLevel, 2026f). Waits control when the next step runs. Actions do the work: Send SMS, Send Email, Add Contact Tag, Create/Update Opportunity, Send Internal Notification and dozens more (HighLevel, 2026a).

Branching is handled by the If Else action, which sends a contact down different paths based on a condition, such as whether they have a tag or replied. Goal Event lets a contact jump ahead when they reach a goal, for example booking a call halfway through a follow-up sequence.

Three blocks in a row labelled Trigger, Wait and Action, showing the order every GoHighLevel workflow runs in
A trigger starts the run, waits control the timing, and actions do the work.

To start one, open Automation, then Workflows, and pick Create Workflow to build from scratch, Browse Templates for a prebuilt recipe, or Build using AI to describe it in plain words (HighLevel, 2026b). Then select Add New Trigger, add filters so the trigger only fires for the right contacts, and add your actions below it. Nothing runs until the workflow is published.

Which settings stop double texts?

Allow Re-entry and Stop on Response cause most double texts, and Time Window, Timezone and Sender Details cause most of the rest, so set all five before you add a single action. They sit on the Settings tab of every workflow (HighLevel, 2026c).

SettingWhat it doesOur default
Allow Re-entryLets a contact run the workflow again after finishing or being removedOff, unless the job repeats by design
Stop on ResponseEnds the workflow for a contact who replies to one of its messagesOn for every follow-up sequence
Time WindowHolds texts and emails until the hours you allowBusiness hours in the contact’s timezone
TimezoneUses your account’s timezone or each contact’s ownContact’s timezone if you serve several regions
Sender DetailsSets the from name, email and number for the workflowYour main business number and name

One detail catches almost everyone. Appointment and invoice triggers always allow re-entry, whatever the setting says (HighLevel, 2026c). A customer who reschedules twice can get three confirmations unless your messages read sensibly when repeated.

Recipe 1: How do you reply to a new lead instantly?

Reply within minutes, because speed decides whether a lead becomes a conversation. The MIT and InsideSales study found the odds of qualifying a web lead were 21 times higher when contact came within 5 minutes instead of 30 (Oldroyd and InsideSales, 2007). Our guide on how fast you reply to new enquiries covers the research.

  1. Trigger: Form Submitted, filtered to your enquiry form.
  2. Action: Create/Update Opportunity in your sales pipeline, stage “New lead”.
  3. Action: Send SMS: “Hi [First name], thanks for getting in touch with [Business]. What’s the best time for a quick call today? Or book here: [booking link]”
  4. Action: Send Internal Notification to the person who handles leads, with the contact’s name and phone number.
  5. Wait: The contact to reply, with a Timeout of 1 day.
  6. Timeout branch: Send SMS: “Hi [First name], just checking you saw this. Happy to answer any questions by text. [booking link]”

Turn Stop on Response on, so a reply ends the workflow and a person takes over.

Recipe 2: How does missed call text back work?

Missed call text back is a built-in feature, not a workflow you build from nothing. Turn it on in Settings, then Phone System, then Voice, then Voicemail & Missed Call Text Back (HighLevel, 2026d). It sends a text to anyone whose call goes unanswered.

  1. Set the incoming call timeout to 10 to 20 seconds, the range HighLevel recommends, so a call counts as missed before it rolls to voicemail.
  2. Write the message: “Sorry we missed your call. This is [Business]. How can we help? Reply here and we’ll get straight back to you.”
  3. Send the test to your own phone and save.

It texts on every missed call, so three calls in five minutes means three texts; HighLevel advises adding a wait of about 20 minutes or a tag filter to the workflow recipe (HighLevel, 2026d). We cover the details on our page about missed call text back.

Recipe 3: How do you send booking confirmations and reminders?

Use one workflow for the confirmation and both reminders, so the timing lives in one place.

  1. Trigger: Customer Booked Appointment, filtered to the calendar this workflow covers.
  2. Action: Send SMS: “Hi [First name], you’re booked with [Business] on [date] at [time]. Reply R if you need to reschedule.”
  3. Wait: An upcoming appointment or booking, Before, 1 day.
  4. Action: Send SMS: “Reminder: your appointment with [Business] is tomorrow at [time]. Reply C to confirm or R to reschedule.”
  5. Wait: An upcoming appointment or booking, Before, 2 hours.
  6. Action: Send SMS: “See you at [time] today. Reply if anything has changed.”

If someone books for later the same day, the 1-day reminder time has already passed; set the wait to skip outbound messages in that case (HighLevel, 2026e). For wording by industry, use our 15 appointment reminder texts.

Recipe 4: What should happen after a no-show?

Ask the person to rebook the same day, while the appointment is still on their mind, and give your team a task to call.

  1. Trigger: Appointment Status, filtered to the status no show.
  2. Wait: A set period of time, 30 minutes.
  3. Action: Send SMS: “Hi [First name], we missed you today. Things come up. Want to pick a new time? [booking link]”
  4. Action: Add Task for the team member who owns the contact: “Call to rebook” due the next business day.
  5. Action: Add Contact Tag “no-show”, so you can see repeat no-shows later.

Recipe 5: How do you ask for reviews automatically?

Ask every customer once the job is done, during hours they will read it.

  1. Trigger: Opportunity Status Changed, filtered to Won. If you track delivery as a pipeline stage instead, use Pipeline Stage Changed, filtered to your “Job complete” stage.
  2. Wait: A set period of time, 2 hours, with Advance Window on and Resume Between Hours set to your business hours, so nobody gets a request late at night.
  3. Action: Send Review Request.
  4. Wait: A set period of time, 3 days.
  5. Action: Send SMS: “Hi [First name], thanks again for choosing [Business]. If you have a minute, a short review helps others find us: [review link]”

Send the request to every customer, not only the happy ones. Google’s Maps content policy lists “selectively solicit positive reviews from customers” as rating manipulation (Google, 2026).

Recipe 6: How do you follow up on stale deals?

A deal that sits in one stage for a week is usually waiting on you, not the customer. This recipe makes the pipeline tell you.

  1. Trigger: Stale Opportunities, filtered to your sales pipeline, with the number of days you consider stale (we start at 7).
  2. Action: Send Internal Notification to the owner of the opportunity: “No movement on [contact] for 7 days.”
  3. Action: Send SMS to the contact: “Hi [First name], just checking in on your quote from [Business]. Any questions I can answer?”
  4. Wait: The contact to reply, with a Timeout of 3 days.
  5. Timeout branch: Add Task “Call or close this deal” for the owner.

Never mark the deal lost automatically; the task makes a person decide.

Recipe 7: How do you reactivate old leads?

Send one honest text to past enquiries who gave you permission to contact them, and route every reply to a person. Run it as a single message, not a blast.

  1. Trigger: Contact Tag, filtered to the tag “reactivate” being added.
  2. Action: Send SMS: “Hi [First name], it’s [Business]. You asked about [service] a while back. Is that still something you need? Reply STOP to opt out.”
  3. Wait: The contact to reply, with a Timeout of 5 days.
  4. Reply branch: Send Internal Notification to your team and Create/Update Opportunity in your sales pipeline at “New lead”.
  5. Timeout branch: Remove Contact Tag “reactivate” and end the workflow.

Leave Stop on Response off for this workflow, because it uses the reply branch: with it on, a reply ends the run before the notification is sent. You start it by filtering a list in Contacts and adding the tag in bulk, in small batches your team can answer.

Which automations should you build first?

Build the new lead reply and missed call text back first, because they catch people ready to talk today. Then add reminders and the no-show follow-up to protect booked time, then review requests, and last the stale deal and reactivation recipes.

Texting to US numbers needs A2P 10DLC registration, and HighLevel’s phone billing guide lists its fees (HighLevel, 2026g). Other countries have their own sender rules, so check yours before launch. Texts, calls and emails are billed by usage, so a workflow that loops costs money as well as goodwill.

How do you test a workflow before it goes live?

Test with your own contact record before you publish. The builder has a Test Workflow button for exactly this (HighLevel, 2025). Create a test contact with your own phone number and email, then fire the real trigger: submit the form, book the appointment, change the opportunity status.

Check that each message arrives once with its merge fields filled in (an empty first name reads as “Hi ,”), that the waits behave (shorten them for the test, then restore them), and that a reply stops the sequence.

What mistakes cause double texts?

Almost every double text comes from two automations answering the same event.

  1. Two workflows on the same trigger. A form that starts both a “new lead” workflow and a “newsletter” workflow sends two welcome texts. Give each trigger one owner, or add filters so they never overlap.
  2. The built-in missed call text back plus your own missed call workflow. Use one or the other.
  3. Allow Re-entry left on for a trigger that fires often, such as a tag that is added and removed by other workflows.
  4. Stop on Response left off, so a customer who replied still gets the next three follow-ups.
  5. Reschedules on appointment triggers, which always re-enter. Write confirmations that make sense if they arrive twice.

Older tutorials and videos sometimes build these steps as campaigns rather than workflows. The current help centre describes the builder as Workflows inside Automation, so if a guide tells you to open a campaign, look for the same steps in the workflow builder.

When should you have it set up for you?

Have it built for you when your time, or the cost of a mistake, is worth more than the setup. Every recipe needs the pipeline, calendar, forms and texting registration to exist first, and every path needs testing.

OmniFlow is built on GoHighLevel and costs $99 a month or $999 a year, with business setup, initial automations and follow-up workflows, and ongoing management included. The team builds your pipeline, booking, forms and first workflows for you, so they are running when you start. You can read how that compares on our page about GoHighLevel set up for you.

Two things are billed separately: texts, calls, email delivery and AI usage are charged by consumption, and AI voice agents, AI chat agents and complex automations are quoted after a scoping call. If you enjoy building workflows yourself, or you are an agency building them for clients, GoHighLevel on its own is the better buy.

GoHighLevel automation questions

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

A trigger is the event that starts a workflow, such as Form Submitted, Customer Booked Appointment or Opportunity Status Changed. An action is a step the workflow takes after it starts, such as Send SMS, Add Task or Create/Update Opportunity. Every workflow has at least one trigger and runs its actions in order, with waits and If Else branches deciding timing and path.

Does GoHighLevel have workflow templates?

Yes. When you create a workflow you can choose Browse Templates to start from a prebuilt recipe, Create Workflow to start from scratch, or Build using AI to describe the workflow in plain words and let the builder draft it (HighLevel, 2026b). Check every filter, wait and message in a template before you publish it.

Can GoHighLevel automations send texts at night?

Only if you let them. The Time Window setting on each workflow holds texts and emails until the hours you allow, and the Timezone setting can use each contact’s own timezone, so a 9pm send waits until morning (HighLevel, 2026c).

Do GoHighLevel automations cost extra?

Workflows are part of every GoHighLevel plan, but the messages they send are billed by usage. HighLevel’s phone billing guide prices text segments, call minutes and numbers on top of the plan, and inbound texts carry a rate too (HighLevel, 2026g). Test with your own number and watch usage in the first weeks.

Start with one recipe

Pick the recipe where you lose the most today, usually the new lead reply, build and test it, then add the next. If you would rather have your workflows built and tested for you, book a 15-minute walkthrough and we will show you what the setup covers.

References

Keep exploring

All insights
An agency client onboarding checklist on a laptop with the first steps already ticked by automation

Agency Operations

Client Onboarding Checklist for Agencies, With a Template

The 10 steps an agency runs between a signed contract and a productive kickoff, the extra checks an SEO client needs, and a day by day template you can copy.

By OmniFlow Editorial Team Oct 5, 2026 9 min read

Read article
A phone showing an appointment reminder text with confirm and reschedule replies beside a small booking calendar

Guides

Appointment Reminder Text: 21 Templates, With Confirmations

Copy-ready appointment reminder and confirmation texts by industry, each counted to fit one SMS, with a timing table, three no-show texts and the opt-out rules to keep.

By OmniFlow Editorial Team Oct 22, 2026 10 min read

Read article
OmniFlow

Put the insight to work

Build a more connected operation

See how OmniFlow can bring your pipeline, communication, booking and follow-up into one configured workspace.

Book a free demo