🥳 Celebrate Our Launch With a $200 LIFETIME Discount OFF The Premium Plan Use: BIRTHDAY2024

This offer expires 9/30/2024, at 11:59 PM EST

BizStackPro all-in-one digital marketing platform dashboard.
Workflow Action: Go To – BizStackPro Help

BizStackPro Help Center · Workflows & Automation

Workflow Action: Go To

Use the Go To action to redirect a contact to a different point in your workflow so you can simplify complex automations and reduce duplicate steps.

Simplifying Complex Workflows Instead of Duplicating The Same Steps Everywhere

Workflow automation can become difficult to manage when multiple branches require the same actions, customer journeys overlap, or contacts need to skip unnecessary steps based on their behavior.

BizStackPro's Go To workflow action allows businesses to redirect contacts to another point within the same workflow, helping reduce duplication and simplify automation design.

Without workflow routing tools, businesses may create oversized automations, duplicate follow-up sequences, increase maintenance requirements, or make troubleshooting more difficult as workflows grow.

This guide explains how the Go To workflow action works, when workflow redirection should be used, and how to build cleaner automation systems inside BizStackPro.

Before redirecting contacts within a workflow, it helps to understand how workflow paths, branching logic, conditions, automation routing, workflow organization, and customer journey management work together inside BizStackPro.

What this workflow action does

The Go To action lets you send a contact to a specific point within the same workflow. It’s especially helpful in larger automations where you want to route contacts based on behavior, tags, or conditions—without copying the same steps across multiple branches.

Best for: Re-using one clean follow-up path, skipping steps a contact no longer needs, and keeping your workflow builder easier to maintain.

Important rules for using Go To

  • End-of-path only: Go To can only be used at the end of a workflow path.
  • Works at branch endings: It can be used at the end of an If/Else branch (because that branch is its own path).
  • Pick a destination: After saving, you select the step where the contact should continue.

Why this matters: Keeping Go To limited to end-of-path routing prevents confusing mid-path jumps and helps keep automations predictable.

Step-by-step: How to use the Go To action

  1. Open your workflow: Go to Automation → Workflows, then open the workflow you want to update.
  2. Add Go To at the end: Click Add Action at the end of the workflow path (or at the end of an If/Else branch).
  3. Select Go To: Choose Go To from the actions list and click Save.
  4. Choose the destination: Click the step in the workflow where you want the contact to continue.
  5. Publish and test: Publish the workflow and test both branches to confirm routing behaves as expected.

Reminder: You won’t be able to place Go To in the middle of a path—if you need a jump, move it to the path ending.

How to confirm it’s linked correctly

You’ll know the Go To action is configured correctly when you see both of the following in the workflow builder:

  • A green circle appears under the Go To action.
  • A dotted line shows where the contact will be redirected.

Tip: If you don’t see the dotted line, re-check that Go To is placed at the end of the path and that a destination step has been selected.

How to unlink and choose a different destination

If you need to change where Go To sends contacts:

  1. Click the Disconnect GoTo icon under the Go To action.
  2. Select a new destination step in the workflow.
  3. Confirm the green circle + dotted line appear again.

Example: Avoid duplicate abandoned cart emails

Scenario: An online retailer wants to recover abandoned carts, but does not want to send follow-up emails to customers who already purchased.

Trigger

  • Abandoned Checkout
  • Duration: 10 minutes
  • Cart Value: > $50

Main actions

  • Email reminder + incentive
  • Wait 1 day
  • If/Else: check “Purchased” tag

Go To usage

  • If Purchased tag exists
  • Use Go To to skip ahead to the “Wait” step
  • Prevents duplicate follow-up emails

Outcome: The workflow attempts to recover abandoned carts while avoiding unnecessary emails to customers who already purchased.

Pro tips

  • Use Go To to reduce duplication: Build one clean follow-up path and route contacts into it as needed.
  • Watch for loops: If routing backward, ensure your conditions prevent repeated cycling.
  • Name steps clearly: It makes selecting destinations faster and reduces mistakes.
  • Test both scenarios: Run tests for “purchased” and “not purchased” paths before going live.

Build cleaner automations without duplicating steps

Go To helps you route contacts into the right place at the right time—so your workflows stay simple, scalable, and easy to maintain.

Frequently Asked Questions

Where can I use the Go To action in a workflow?

The Go To action can only be used at the end of a workflow path (including at the end of a branch inside an If/Else condition). From there, it directs the contact to a specific point within the workflow.

Can I use the Go To action in the middle of a workflow path?

No. The Go To action is restricted to the end of a workflow path.

How do I know if the Go To action is set up correctly?

In the workflow builder, a green circle appears under the Go To action and a dotted line shows the redirection path.

How can I change the action for a contact after it’s been set?

Click the “Disconnect GoTo” icon under the Go To action, then select a new action where you want the contact to proceed.

Route contacts smarter with Go To

Use Go To to keep workflows lean, avoid duplicated branches, and maintain predictable automation paths—especially as your logic grows.

✅ View Plans & Features

Cleaner workflows. Less duplication.

Disclaimer: This site is NOT endorsed by Google, Facebook or YouTube in ANY WAY. All trademarks & Logo / branding are the property of their respective owners. Please Note: This site was created in BizStackPro by Ken George II (An Affiliate of BizStackPro) and may contain affiliate links.

All About BizStackpro


Copyrights 2024 | AllAboutBizStackPro.Com | Pricing | About | Features | All Rights Reserved.