Multi-path branching
Map a single decision to several possible workflow paths using case branches.
Selection component
Selection for customer-owned automation.
Use Selection when a decision has more than two possible outcomes.
Route a workflow through multiple branches by evaluating an input value against cases.
Selection
Component
SelectionEvaluate one input against multiple cases and route to the matching branch or default.
CX
CXFabric Flow
Rules, credentials, validation, audit
SettingsInputs and options
LogsRun history and output
Next stepConnector, component, or approval
What this component unlocks
Use Selection as a visible flow step.
The docs describe Selection as flexible branching logic for multiple paths, unlike the binary setup of Conditional. Builders configure an input value, an operator, branch values, and a default branch that is followed when no case matches. Additional branches can be added with the Add Branch control, and each branch can have its own connected downstream components.
Default handling
Send unmatched values to a known fallback path instead of failing silently.
Operator-based matching
Use comparison, contains, list membership, starts with, and ends with operators to route execution.
Use cases
Where Selection fits in automation.
These examples show how this component can become part of production workflows across customer-owned systems and environments.
Queue routing
Use Selection 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
Customer tier handling
Use Selection 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
Record type switch
Use Selection 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
Language routing
Use Selection 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
Provider selection
Use Selection 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
Error category handling
Use Selection 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 Selection 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.
Enter input value
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Choose operator
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Add branches
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Configure default branch
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Connect branch components
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
Always configure a clear default branch
Always configure a clear default branch.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Make sure input values and branch values are compatible
Make sure input values and branch values are compatible.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Test multiple values to confirm each branch routes as expected
Test multiple values to confirm each branch routes as expected.
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 Selection.
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
Selection in a customer intake flow
Start with an event, use Selection, then route the result to CRM, ticketing, or a customer-owned system.
Selection with approval and audit
Add validation, human approval, and logging around the component before downstream actions execute.
Selection in a private runtime
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
Selection plus custom connector
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
Need Selection inside a customer workflow?
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.