How to Build Workflows in GoHighLevel: A Step-by-Step Guide

Learning how to build workflows in GoHighLevel is the most valuable skill on the platform. Workflows decide what happens when a lead fills in a form, books a call, misses an appointment, pays an invoice or replies to a message. Built well, they quietly do hours of work every week. Built badly, they send the wrong message to the wrong person at the wrong time.

This guide explains the building blocks of the GoHighLevel workflow builder and walks through creating a workflow from plan to publish. For a complete real-world example, see our guide on how to automate lead follow-up in GoHighLevel.

How GoHighLevel workflows work

Every workflow has the same basic shape:

• Trigger — the event that starts the workflow, such as a form submission, a new appointment, a tag being added or a pipeline stage change.
• Filters — conditions on the trigger that narrow who enters, such as “only this form” or “only contacts with this tag”.
• Actions — what happens next: send an SMS, email or WhatsApp message, add a tag, create a task, notify a user, update an opportunity and much more.
• Logic — waits, if/else branches and goals that control timing and paths.
• Settings — rules that apply to the whole workflow, such as re-entry and stopping when a contact replies.

Workflows live in the Automation section of each sub-account. You can start from scratch or from one of HighLevel’s ready-made recipes, then adapt it.

Step 1: Plan the workflow on paper first

The biggest workflow problems start before anyone opens the builder. Write down, in plain sentences:

1. What starts it? (“When someone submits the consultation form…”)
2. Who should it apply to? (“…but only new contacts, not existing clients.”)
3. What should happen, in order? (“Reply instantly, notify Priya, wait, follow up…”)
4. What should stop it? (“…unless they reply or book.”)
5. What does success look like? (“A booked appointment.”)

Step 2: Add the trigger and filters

Create a new workflow, give it a clear name (for example “Lead – Website form – Follow-up”), and add a trigger. Common triggers include:

• Form Submitted or Survey Submitted — for website and funnel forms.
• Appointment Status — when an appointment is booked, confirmed, cancelled or marked as a no-show.
• Contact Tag — when a tag is added or removed.
• Pipeline Stage Changed or Opportunity Status Changed — for sales processes.
• Customer Replied — when a contact sends a message.
• Call Status — useful for missed calls.
• Invoice or payment events — for billing follow-up.

Then add filters. A trigger without filters can fire far more often than you expect — for example, every form on the account instead of just one.

Step 3: Add actions

Click the plus sign below the trigger to add actions. The ones you’ll use most:

• Send SMS / Send Email / WhatsApp — the messages themselves, personalised with custom values such as the contact’s first name.
• Internal Notification — alerts a team member by email, SMS or in-app notification.
• Add/Remove Tag — labels contacts so other workflows and reports can use them.
• Create/Update Opportunity — moves leads through your pipeline.
• Assign to User — gives each lead a clear owner.
• Add Task — reminds someone to call or check something.
• Update Contact Field — saves information for later steps.
• Webhook — sends data to another system.

Step 4: Control timing and paths

Wait steps

Wait steps pause the workflow for a set time, until a specific time or day, or until a condition is met (such as a reply). Use them to space out follow-ups and to keep messages within business hours.

If/Else branches

If/Else checks a condition — a tag, a field value, an appointment, a reply — and sends the contact down different paths. For example: if the lead chose “Shopify store”, send the Shopify message; otherwise send the general one.

Goal events

A goal event lets a contact skip ahead or leave the workflow once something happens, such as booking an appointment or making a payment. This is how you stop chasing people who have already done what you wanted.

Step 5: Check the workflow settings

• Allow re-entry — decides whether the same contact can go through the workflow more than once. Usually off for welcome sequences, sometimes on for repeat events.
• Stop on response — ends the workflow when the contact replies. Essential for follow-up sequences.
• Time window — limits when messages can go out.
• Sender details — the name, email address and phone number messages come from.

Step 6: Test before publishing

New workflows start in draft. Before you publish:

1. Use the workflow’s test option, or trigger it for real with a test contact using your own phone and email.
2. Check each message arrives with the right name, links and sender.
3. Test every branch — including the reply and booking paths that should stop the workflow.
4. Open the execution logs to see exactly which steps ran and why.
5. Shorten wait times temporarily while testing, then set them back.

When everything works, switch the workflow from Draft to Publish and save.

Keep workflows organised as you grow

• Use a naming system — area, source and purpose, such as “Appointments – Reminders” or “Leads – Facebook – Follow-up”.
• Group workflows in folders by area: leads, appointments, customers, internal.
• Document the purpose of each workflow in a short note.
• Review regularly and switch off old workflows that no longer apply.
• Avoid overlapping workflows that send different messages to the same contact for the same event.

Five workflows most businesses should build first

1. New lead follow-up — instant reply, team alert and a short follow-up sequence.
2. [Missed-call text-back](/blog/missed-call-text-back) — an instant text to callers you couldn’t answer.
3. [Appointment reminders](/blog/appointment-reminder-automation) — confirmation, reminders and no-show follow-up.
4. Review requests — a request after each completed job or visit.
5. Long-term nurture — occasional helpful messages for leads who aren’t ready yet.

Common GoHighLevel workflow mistakes

• Triggers without filters, so the workflow fires for the wrong contacts.
• Forgetting stop rules, so people keep getting messages after they reply or book.
• Waits that ignore business hours.
• Re-entry left on by accident, so contacts get the same sequence twice.
• Publishing without testing every branch.
• Texting before SMS registration is complete — see our A2P 10DLC registration checklist.

Want your workflows planned, built and tested for you? Tocal has worked on 50+ GoHighLevel accounts over 3+ years. Our GoHighLevel service covers workflows, pipelines, calendars and messaging setup — with fast delivery and reasonable pricing. Book a free call to talk through what you need.