Start here
Guide

Workflows in GoHighLevel: a practical introduction

15 September 2026 · 3 min read

Workflows are where GoHighLevel stops being a fancy address book and starts earning its subscription. They’re also where people build 40-step monsters that break in ways nobody can debug.

This guide is the middle path: what the builder actually does, and the small set of workflows that cover 90% of real needs.

The mental model

A workflow is three things:

  1. A trigger — the event that starts it: form submitted, stage changed, appointment booked, inbound SMS, “customer replied”.
  2. A filter (optional) — the conditions under which it runs: only for this pipeline, only for this tag, only in business hours.
  3. A sequence of actions — send SMS, wait, send email, add tag, update contact, notify the team, start another workflow.

The critical discipline: one workflow, one job. A workflow that handles new leads and nurture and review requests and reactivations is four workflows welded together. When one branch breaks, all four stop working. Build small, name them clearly, and let them call each other (the “Start Workflow” action) when they need to chain.

The four workflows every business needs

1. New lead instant reply

Trigger: form submission or inbound call.

  • Send SMS/email within a minute: “Got your enquiry, we’ll be with you shortly” + booking link if appropriate.
  • Notify the assigned team member.
  • Add the lead source as a tag, so you can later see which forms actually produce customers.

Speed-to-lead is the whole game. An instant reply doubles contact rates; a 4-hour reply might as well be never.

2. Follow-up sequence

Trigger: pipeline stage change to “Quoted” (or your equivalent).

  • Day 2: “Any questions about the quote?”
  • Day 5: a useful piece of content (case study, FAQ, “what happens on the day”).
  • Day 10: “Still interested? No pressure either way.”
  • Day 14: move to long-term nurture if no reply.

The wait steps between actions are where the magic is — GHL keeps the timer even if the contact replies, so add a goal/exit filter: “if stage is no longer Quoted, stop”.

3. Appointment reminders

Trigger: appointment booked.

  • 24 hours before: SMS reminder with the time (the calendar handles the timezone).
  • 1 hour before: second SMS.
  • No-show detection: appointment status → no-show → trigger a “sorry we missed you, reschedule?” workflow.

No-show rates drop by half with one reminder SMS. This is the highest ROI workflow in the platform.

4. Review request after completion

Trigger: stage change to “Completed”/“Job done”, or a form/checkbox your team ticks on site.

  • Wait 24 hours (gives the job time to bed in).
  • Send the review link — SMS for consumers, email for B2B.
  • One follow-up after 3 days if no review. Then stop. Chasing harder annoys the happy customers into silence.

Building habits that keep you sane

  • Name workflows like documents, not experiments: “NEW LEAD — instant reply + notify” not “test v3 final FINAL”.
  • Test with a real contact — send a test form submission from your own phone and watch it flow. The history tab shows every step, which one fired, and any errors.
  • Version in your head, not in the builder: clone a workflow before a big edit, verify the clone, then delete the old one. Renaming “v3” every week is how you end up with eleven workflows and no idea which is live.
  • Watch the error log weekly: Automation → Workflows → Errors. It’s quiet when everything’s healthy; any entries mean an action is failing (usually an integration token expired or a template references a deleted custom field).

That’s the honest introduction. Pipelines and calendars feed workflows; workflows are the automation engine. Get those three right and you have a working CRM — everything else is refinement.

← All guides