Feature deep-dive
Workflows & automations
Workflows are the engine room. The CRM stores the lead; the funnel captures it; the workflow is the thing that actually makes money, because it texts that lead in sixty seconds at 11pm on a Sunday when nobody is at the desk. Everything else in GoHighLevel is a feature. This is the product.
How a workflow is built
A workflow is a canvas. You add one or more triggers, then chain actions below them, with conditions that split the path and waits that hold a contact until a time, a date, or an event.
Triggers — what starts it
There are dozens. The ones that matter in practice: form submitted, survey submitted, funnel page visited, inbound SMS received, call missed, appointment booked, appointment status changed (this is how no-show recovery works), pipeline stage changed, tag added or removed, contact created, birthday or custom date reached, payment received, invoice sent, Facebook or Google lead-form submission, and an inbound webhook from anything at all.
Triggers accept filters, so "form submitted" can mean "the consultation form, only when the budget field is over $5,000, only from the paid-search source." That filtering happens before the workflow runs, which keeps the logic clean.
Actions — what it does
Send SMS. Send email. Place a call and connect it to a rep. Drop a ringless voicemail. Send a WhatsApp or Messenger message. Add or remove a tag. Update any contact field. Create or move an opportunity. Assign to a user (with round-robin). Create a task. Add to another workflow, or remove from one. Send an internal notification. Fire a webhook. Run a Google Sheets or Slack action. Hand the conversation to Conversation AI. Run a premium AI step — Decision Maker, Intent Detection, Summarize Text, Translate — that lets a language model make a branching decision inside the automation.
Control flow — where the skill lives
If/else conditions branch on anything in the record. Wait steps hold for a duration, until a specific time of day (so your 3am automation texts at 9am), or until an event occurs ("wait until appointment is booked, up to 48 hours"). Goals pull a contact out of the sequence the moment they convert, which is what stops the classic embarrassment of a customer receiving "still thinking it over?" the day after they paid you. Math and array operations let you do lead scoring without an external tool.
The one workflow that pays for the subscription
Ignore the hundred-step monsters people sell in snapshot packs. This is the automation that moves revenue, and it takes ten minutes:
- Trigger: form submitted, or call missed.
- Action: send an SMS immediately — "Hi {{contact.first_name}}, this is Sam at the clinic, sorry we missed you. Want me to grab you a slot this week?"
- Wait: 5 minutes, unless they reply.
- Action: send an email with the booking link.
- Action: create an opportunity in the New Lead stage and notify the owner.
- Goal: appointment booked → exit the workflow.
- Else: one more text at 24 hours, one at 72 hours, then stop.
Speed-to-lead is the most reliably profitable thing a local business can fix, and this is the cheapest way to fix it. See missed-call text back for the version that requires almost no configuration at all.
Who it is for
Anyone whose follow-up currently depends on a human remembering. In practice: agencies building the same nurture sequences repeatedly across clients (build once, ship with a snapshot), and any business where the lead goes cold in under an hour — home services, clinics, med spas, legal intake, real estate.
Workflows vs buying Zapier or Make
The question is not which builder is more powerful in the abstract. Zapier connects to 6,000 apps and GoHighLevel does not. The question is where your automation lives.
| Feature | GoHighLevel Workflows | Zapier / Make |
|---|---|---|
| Triggers on GHL events | Native, instant | Polling or webhook, with lag |
| Cost per run | Included (AI steps metered) | Task-based pricing, adds up fast |
| Sends SMS / email natively | Included | Needs a separate paid app |
| Reads the full contact record | Included | Only the payload you pass |
| Connects to 6,000+ apps | Not included | Included |
| Breaks when a vendor rotates a key | No — same database | Yes, regularly |
| Branching + conditions | Included | Included |
| Version history / rollback | Limited | Limited |
| Error visibility | Per-contact execution log | Task history + email alerts |
The two are complements, not substitutes. Most agencies run workflows natively and keep a small Zapier plan for third-party edges — see integrations.
Where workflows fall short
- Debugging is painful. There is an execution log per contact, and it will tell you which step ran — but tracing why a contact took the wrong branch across a workflow with thirty steps and four conditions is genuinely tedious. There is no step-through debugger, no dry-run against a cohort, and no diff between versions.
- Version control is thin. You get draft/publish, not a proper history you can roll back to. If a colleague edits a live workflow and breaks it, your recovery path is remembering what it used to look like.
- It is very easy to build a mess. The builder does not stop you creating overlapping workflows that all text the same contact. The classic failure is a lead getting four texts in ten minutes from four different automations, because nobody owned the enrolment logic. Discipline — naming conventions, one entry point per journey, aggressive use of goals — is on you, not the tool.
- Sends cost money and the builder does not warn you. Nothing in the canvas says "this branch will cost $340 a month at your current volume." Model the send cost before you publish; see the usage-cost table.
- No native error handling or retries on webhooks. If your endpoint is down when the webhook fires, the workflow shrugs and continues. Anything mission-critical should be queued on your side, not trusted to a fire-and-forget step.
- Premium AI steps meter per execution. A Decision Maker step in a workflow that runs on every inbound message is a recurring bill, not a one-off. Fine — just know that before you sprinkle them everywhere.
The honest summary
The workflow builder is not the most elegant automation tool on the market — n8n and Make are better engineering tools, and it shows. It wins for a specific and decisive reason: it is already inside the database that holds your leads, your calendar, your pipeline, and your phone number. No API keys, no polling delay, no integration that silently dies on a Tuesday. For follow-up automation on top of a CRM you already own, that beats elegance every time.
Keep reading
Related features
-
All GoHighLevel features
The full feature hub — every module, honestly scored.
-
CRM & pipelines
Contact records, custom fields, smart lists, opportunity pipelines, and a unified inbox where SMS, email, and social DMs all land on the same timeline.
-
Integrations & Zapier
Native connections to Stripe, Google, Meta, Shopify, QuickBooks and Zoom, plus Zapier/Make and a developer app marketplace.
-
Pricing & usage costs
Workflows send SMS and email. Those sends are metered. Here is what they cost.
Frequently asked questions
- What are GoHighLevel workflows?
- Workflows are GoHighLevel's visual automation builder. Each workflow starts with one or more triggers (a form submission, an inbound call, a pipeline stage change, a tag being added, a date), then runs a sequence of actions — send SMS, send email, wait, branch on a condition, move a pipeline stage, create a task, call a webhook, hand off to an AI agent — on the contact that entered it. It is the engine that turns the CRM from a filing cabinet into a follow-up machine.
- What is the difference between workflows and campaigns in GoHighLevel?
- Campaigns are the older, linear drip system: a fixed sequence of messages on a fixed schedule. Workflows replaced them and are strictly more capable — branching, conditions, math operations, webhooks, AI steps, goals, and multiple triggers. Build everything new in Workflows; Campaigns exist mainly for backwards compatibility with older accounts.
- Are GoHighLevel workflows included in the plan price?
- The workflow builder itself is included in every plan, including the $97 Starter. What is not included is what the workflow does: each SMS segment, email, voice minute, and AI step is metered against your prepaid wallet. Premium AI actions inside workflows — such as Decision Maker, Intent Detection, Summarize Text and Translate — are billed per execution, at roughly a cent each at current published rates.
- Can GoHighLevel workflows replace Zapier?
- For anything that happens inside GoHighLevel, yes — and they should, because a native trigger is faster and does not break. For connecting GoHighLevel to a third-party app that has no native integration, you still need Zapier, Make, or a custom webhook. In practice most agencies use workflows for 90% of automation and keep a small Zapier account for the edges.
- How many workflows can I build?
- There is no published cap on the number of workflows in a sub-account, and agencies routinely run dozens per client. The practical limit is comprehension, not quota: a sub-account with sixty overlapping workflows and no naming convention is unmaintainable, and untangling one is the single most common paid clean-up job in the GoHighLevel ecosystem.
- Can I test a workflow before it goes live?
- Yes. Workflows have a draft/publish state, and you can run a test with a specific contact to walk them through the steps. Use it — an unpublished workflow does nothing, and a published workflow with a mis-set wait step can text a thousand people at 3am. Always test with your own phone number first.
Build the five-minute speed-to-lead workflow
Start a trial, connect a number, and build the missed-call text-back automation above. If it books one extra job this month it has paid for the platform — and you will have learned the builder properly in the process.
Affiliate link. We earn a commission at no extra cost to you.