×

GoHighLevel Workflow Go To Action

/ CRM, GHL / By

How to Use the Workflow Go To Action in GoHighLevel

If you are building automations in GoHighLevel and previously managed projects in ClickUp, you will appreciate how the Workflow Go To action lets you organize complex journeys without duplicating steps. This feature helps you move contacts between actions and branches while keeping your workflows clean and easy to maintain.

This how-to guide explains what the Go To action does, how to configure it, and how it behaves in common scenarios so you can design reliable automation in GoHighLevel.

What the Go To Action Does in GoHighLevel

The Workflow Go To action in GoHighLevel allows you to send contacts to another action or branch within the same workflow. Instead of recreating the same logic multiple times, you can jump from one point to another and keep all actions connected.

Key capabilities of the Go To action include:

  • Jumping forward or backward to another action.
  • Connecting to a specific branch of a previous condition.
  • Keeping contacts inside the same GoHighLevel workflow without cloning it.

Because the Go To action works only inside a single workflow, it is best used for complex automations where you want to reuse logic. For cross-workflow movement, you would still rely on other tools and entry triggers within GoHighLevel.

Where to Add the Go To Action in GoHighLevel

You can place the Go To action almost anywhere in a workflow as long as the target action or condition already exists. The logic is visual and is handled entirely inside the workflow builder.

To add the Go To action in GoHighLevel:

  1. Open the Workflows section.
  2. Select or create the workflow you want to edit.
  3. Hover between two actions where you want to insert a new step.
  4. Click the + icon to add an action.
  5. Choose Go To from the list of actions.

Once added, you will configure which action or branch the Go To step should send the contact to.

Configuring the Go To Action in GoHighLevel

After adding the Go To step, you must select a target. The configuration interface in GoHighLevel is simple but very specific:

  1. Click on the new Go To action in the workflow.
  2. Under the Go To Action settings, open the dropdown list.
  3. Select the action or condition branch you want to jump to.
  4. Save the workflow.

Only actions and branches above the Go To step in the workflow can be selected. The list will show both regular actions and condition branches that are valid targets.

Supported Targets for Go To in GoHighLevel

The Go To action can send contacts to:

  • Any previously created standard action (such as Send SMS, Wait, or Email).
  • One of the branches (Yes/No or other labeled branches) of a previous conditional step.

This makes it possible to re-enter earlier logic or reuse decision trees without recreating them in GoHighLevel.

Using Go To with Conditions in GoHighLevel

The most powerful use of Go To in GoHighLevel is with condition steps, such as If/Else or other branch-based evaluations. You can send a contact directly into the Yes branch or the No branch of a prior condition from a later point in the workflow.

To use Go To with a condition:

  1. Create your condition step early in the workflow.
  2. Build out the branches you want to reuse.
  3. Later in the workflow, add a Go To action.
  4. When selecting the target, pick the labeled branch under that condition (for example, Condition A – Yes).

When a contact hits this Go To step, GoHighLevel sends them directly into the branch you select, as if they had just passed through that condition again.

Example Scenario with GoHighLevel Conditions

Imagine this simplified flow built in GoHighLevel:

  1. Trigger: Contact added to a specific campaign.
  2. Condition: Has the contact replied?
  3. Yes branch: Send a follow-up and wait 1 day.
  4. No branch: Send a different reminder and wait 1 day.
  5. Later in the workflow, add a Go To action.
  6. Configure Go To to jump to the No branch of the earlier condition.

If a contact triggers the Go To action, they are redirected to the No branch logic under the original condition, without you needing to rebuild that flow.

Behavior Rules of the Go To Action in GoHighLevel

There are some important behavior rules to keep in mind when using Go To in GoHighLevel workflows. These rules prevent loops and protect the integrity of your automations.

Go To Can Only Target Previous Steps

The Go To action can only point to actions or branches above it in the workflow. Actions created below the Go To step will not appear as selectable targets.

This rule helps avoid infinite loops and ensures each contact follows a predictable path in GoHighLevel workflows.

Skipping the Go To Action Is Not Possible

When a contact reaches a Go To step, they cannot “pass through” it. Instead, one of two things will happen:

  • If the contact has not already passed through the target action or branch, they will be sent there.
  • If the contact has already passed through the target action or branch earlier in this workflow, the contact will immediately exit the workflow.

This automatic exit behavior prevents contacts from re-entering the same branch or action multiple times and creating circular paths inside GoHighLevel.

How Go To Handles Contacts Already in the Target Branch

If a contact is already within a branch that includes the Go To action, and that Go To is configured to send them to the same branch or a step they have already passed, they will not loop. Instead, GoHighLevel recognizes the repeat and ends their journey in that workflow at that point.

As a result, you should plan your workflow so that Go To steps always send contacts to earlier logic that they have not yet encountered.

Best Practices for GoHighLevel Workflow Design

To get the most out of the Go To action in GoHighLevel, follow these best practices:

  • Map your workflow on paper first. Identify branches and steps you may want to reuse before you build in GoHighLevel.
  • Create key conditions early. Place important condition steps near the top of the workflow so later Go To actions can reference them.
  • Avoid complex nesting. Keep the number of nested conditions manageable so Go To targets are easy to understand.
  • Use clear labels. Name your conditions and actions descriptively so you can quickly recognize them when setting the Go To target.
  • Test with sample contacts. Run tests in GoHighLevel to confirm that contacts are sent to the expected branch and do not exit prematurely.

Troubleshooting the Go To Action in GoHighLevel

If your Go To action does not behave as expected in GoHighLevel workflows, check these common issues:

  • Target not visible: Ensure the desired action or branch is placed earlier in the workflow than the Go To step.
  • Contacts exiting the workflow: Verify whether those contacts already passed the target step earlier in their journey.
  • Unexpected branch behavior: Confirm you selected the correct branch under the condition (for example, Yes vs No).

For a detailed reference on the original feature description, see the official help article on the Workflow Go To action at this GoHighLevel support page.

Next Steps for Improving Your GoHighLevel Automations

Once you are comfortable using the Go To action, you can combine it with other features in GoHighLevel such as enrollment triggers, pipeline updates, and messaging steps to create powerful automation systems.

If you want strategic help designing scalable workflow architectures, CRM automation, and AI-ready funnels around GoHighLevel, you can learn more at Consultevo.

By mastering the Go To action and its rules, you keep your GoHighLevel workflows flexible, maintainable, and efficient, while avoiding duplicates and confusing paths for your contacts.

Need Help With GoHighLevel?

If you want expert help building, automating, or scaling your GHL , work with ConsultEvo — trusted GoHighLevel Partners.

Scale GoHighLevel

“`