Every GoHighLevel Workflow Action

128 distinct actions across 19 categories, as listed in the workflow builder's Actions panel. An action is a step a workflow performs once something has triggered it — sending a message, changing a field, moving an opportunity, waiting.

Communication is the largest category at 27 actions, spanning email, SMS, voice, and every messaging channel GoHighLevel integrates. Contact and Internal follow at 16 each; Internal is where the control-flow steps live, which is what turns a list of actions into an actual workflow. Conversation AI has grown into its own category at 8, separate from the Conversation AI entry that also appears under Communication.

Grouped as the builder groups them. Names are reproduced exactly, including the BETA markers GoHighLevel attaches to some of them.

Many of these actions have a direct API equivalent, and knowing which is the difference between automating something in an afternoon and rebuilding it in the wrong place. Broadly: the Contact, Communication, and Opportunity actions map onto published endpoints; the control-flow steps in Internal do not, because they only mean something inside a running workflow.

Add Contact Tag corresponds to POST /contacts/:contactId/tags, Update Contact Field to PUT /contacts/:contactId, and the messaging actions to the conversations endpoints. What has no API equivalent is the workflow itself — no published endpoint reads or writes its steps, as covered in the triggers guide.

The useful rule for choosing between them: workflows are for ongoing behaviour, the API is for one-off changes. A rule that should keep applying to every new contact belongs in a workflow, where it runs unattended. A backfill across 4,000 existing contacts is a batching problem — enrolling them all into a workflow to change one field is slower, harder to verify, and harder to stop halfway.