Target flow routing
Redirect execution to a valid flow selected from available platform flows.
Go To component
Go To for customer-owned automation.
Use Go To when execution should move to a selected flow and entry-point component at runtime.
Redirect execution to another component or flow to keep complex processes reusable.
Go To
Component
Go ToRedirect execution to a valid target flow and one of its entry-point components.
CX
CXFabric Flow
Rules, credentials, validation, audit
SettingsInputs and options
LogsRun history and output
Next stepConnector, component, or approval
What this component unlocks
Use Go To as a visible flow step.
The docs describe Go To as a component for dynamically switching execution to a different component or flow within a workflow. Builders select a target flow and then select a target component from that flow; only components configured as entry points are selectable. The docs position Go To for error handling, conditional processing, and looping processes where a set of steps repeats until a condition is satisfied.
Entry-point targeting
Choose an entry-point component inside the target flow so the handoff starts in the right place.
Loop and error patterns
Support error handling, conditional processing, and controlled looping paths.
Use cases
Where Go To fits in automation.
These examples show how this component can become part of production workflows across customer-owned systems and environments.
Error handling
Use Go To as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Reusable approval path
Use Go To as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Looping process
Use Go To as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Shared validation
Use Go To as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Escalation path
Use Go To as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Fallback workflow
Use Go To as part of a governed CXFabric workflow that keeps configuration, credentials, logs, and handoffs visible.
- Collect the approved input
- Apply customer-specific rules
- Pass a clear result to the next step
Configuration surface
Practical options builders expect to use.
The exact fields can vary by deployment and product version, but each page gives customers a clear view of the component's intended role.
Add Go To to canvas
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Open component settings
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Select target flow
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Select target entry component
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Submit configuration
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Hover to review tooltip
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Execute and review logs
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Implementation notes
Design the step with operations in mind.
Components should be easy for builders to configure and easy for operators to understand after the workflow is live.
Current CXFabric docs
Only valid flows and entry-point components should be selectable
Only valid flows and entry-point components should be selectable.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Name target entry points clearly
Name target entry points clearly.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Avoid accidental loops without a clear exit condition
Avoid accidental loops without a clear exit condition.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Workflow patterns
Reusable patterns for Go To.
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
Go To in a customer intake flow
Start with an event, use Go To, then route the result to CRM, ticketing, or a customer-owned system.
Go To with approval and audit
Add validation, human approval, and logging around the component before downstream actions execute.
Go To in a private runtime
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
Go To plus custom connector
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
Need Go To inside a customer workflow?
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.