A workflow is an automation in GoHighLevel. It starts with one or more triggers, such as a form submitted, a tag added, an appointment booked, an opportunity stage changed or an inbound message, and then runs a chain of actions: send an SMS or email, wait, branch on if/else conditions, update a field, add a tag, create a task, move an opportunity, call a webhook and so on. Each workflow is either a draft or published, and only published workflows run.
In practice
You build workflows in the sub-account under Automation, then Workflows (as of October 2026). Add a trigger, add actions below it, test with a real contact, and publish. Workflows can be grouped in folders, and the enrollment history shows which contacts went through and what happened at each step.
Busy sub-accounts collect a lot of workflows: old campaigns, test copies, versions loaded by snapshots. Finding which ones are still published means scrolling through folders, and there's no simple export of the whole list. Agencies doing a cleanup or handing an account over often want a plain list of every workflow and its status first.
Where it shows up in RGS Tools
Sub-Account Manager's workflow list shows every workflow's name and status in one list, and you can filter by name to pull out a set. Blast Follow-Up doesn't require building or changing workflows: the blast finder groups texts sent close together into blasts without campaign IDs or workflow changes.