THEN and ELSE routing
Connect separate downstream steps for the true path and false path so the decision remains visible on the canvas.
Conditional component
Conditional for customer-owned automation.
Use Conditional when the workflow needs a binary decision point that sends work down a THEN or ELSE path.
Evaluate an input value against criteria and route execution through true or false paths.
Conditional
Component
ConditionalEvaluate an input value, operator, and comparison value before routing to THEN or ELSE.
CX
CXFabric Flow
Rules, credentials, validation, audit
SettingsInputs and options
LogsRun history and output
Next stepConnector, component, or approval
What this component unlocks
Use Conditional as a visible flow step.
The docs describe Conditional as a component that evaluates input values against predefined criteria and routes execution based on whether the condition is true or false. Builders configure an input value, an operator, and a value to compare with, then connect components to the THEN path and ELSE path. The operator set includes equality, comparison, contains, list membership, starts with, ends with, empty, boolean, null, and inverse checks.
Operator library
Compare values, check substrings, validate list membership, and test empty, boolean, or null states.
Canvas feedback
Use hover tooltips, action buttons, and logs to review configuration and execution results.
Use cases
Where Conditional fits in automation.
These examples show how this component can become part of production workflows across customer-owned systems and environments.
VIP routing
Use Conditional 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
Consent check
Use Conditional 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
Missing data handling
Use Conditional 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 rule
Use Conditional 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
Retry decision
Use Conditional 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-specific policy
Use Conditional 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 Conditional 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.
Enter comparison value
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Connect THEN path
Expose this behavior as a reusable, logged, credential-aware step inside a CXFabric flow.
Connect ELSE path
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
Ensure input and comparison values use compatible types
Ensure input and comparison values use compatible types.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Use Selection when more than two branches are needed
Use Selection when more than two branches are needed.
CXFabric approachMake the behavior explicit in the workflow so operators can see what happens before and after this component runs.
Test the condition with multiple input values before relying on it in production
Test the condition with multiple input values before relying on it in production.
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 Conditional.
These are concept patterns that can be adapted to a customer's systems, policies, credentials, and deployment model.
Conditional in a customer intake flow
Start with an event, use Conditional, then route the result to CRM, ticketing, or a customer-owned system.
Conditional with approval and audit
Add validation, human approval, and logging around the component before downstream actions execute.
Conditional in a private runtime
Deploy the component inside a customer-owned environment with credentials and logs governed by the customer.
Conditional plus custom connector
Combine the component with packaged connectors or custom APIs when the process needs reusable system logic.
Component planning
Need Conditional inside a customer workflow?
We can scope the workflow, component configuration, credentials, deployment model, and handoff path before buildout begins.