goTo

Overview

The Flow Redirect Component (popularly known as GoTo) is a structural navigation node. Its main function is to end the user's journey in the current automation map and instantly transfer them to the starting point of a completely different automation flow. It acts as a logical bridge that allows process modularization, avoiding the need to build giant, repetitive, or complex flows within a single screen.

Configuration Parameters

The component's parameterization focuses exclusively on defining the user's jump destination within the automation ecosystem:

• Flow: Dropdown menu with a text search field that lists all active automations created in the account. The system administrator must select which destination automation will receive the contact as soon as it reaches this node.

Visual Builder

This component's interface is minimalist and focused on quick indexing to facilitate the architecture of multiple flows:

• Real-Time Paginated Search: The drop-down selector has a search field and a pagination button (Load more), allowing specific flows to be easily located in accounts that have hundreds of automations registered.

• Connection Encapsulation: In the graphical editor, this component usually closes the end of a branch. It has no subsequent output ports in the current flow, since the customer's journey will continue transparently within the new selected flow.

Special Operators

The component's logical properties deal with the persistence of context data and inheritance of variables between different scopes:

• Global Context Persistence: When performing the jump (jump) from Flow A to Flow B, the component keeps all the history of data and variables collected up to that point attached to the contact (e.g.: name, email, or answers provided in previous menus). This ensures that the new flow can read the information without needing to ask the customer everything again.

• Reusable Subroutine Pattern: Allows the concept of functions to be applied in automation. It is possible to create a single flow focused only on a specific task (such as CPF validation or Pix processing) and have multiple other flows point to it through the GoTo whenever they need this action.

Practical Examples

The table below demonstrates classic scenarios of how to structure and connect routines using flow redirection:

Current Flow (Source)	Decision Condition/Context	Selected Destination Flow in GoTo	Practical Use Case
Customer Service Main Menu	Customer typed or chose the "Financial" option.	[Module] Second Copy of Bank Slip	Divert the customer to a specialized and isolated flow that handles only invoice issuance and validation.
Active Marketing Campaign	The lead interacted positively with the mass message.	[Screening] Lead Qualification	Direct the contact who responded to the campaign to a flow focused on collecting profile data and purchase intent.
New Customer Onboarding	Identified that the customer already has an active registration in the system.	[Menu] General Self-Service	Instead of continuing the welcome flow, the system takes the user directly to the general options center.
Any Sales Flow	The customer requests to speak with a human agent after business hours.	[Notice] After Hours	All sales flows direct to this same centralized automation that alerts about the team's absence and collects information for the next day.