Data Conditional Router

The Data Conditional Router lets you split a list of data items into two separate streams—True Output and False Output—depending on whether each item meets a condition you set. It’s useful when you need to separate records that match a rule from those that don’t, without writing code.

How it Works

The component examines each data item you feed into it. For every item it looks at a specific key (the field you name in Key Name) and compares that value to a value you provide in Compare Value. You choose how the comparison is done with Comparison Operator. The possible operators are:

equals – checks if the values are the same
not equals – checks if the values are different
contains – checks if the value contains the compare text
starts with – checks if the value starts with the compare text
ends with – checks if the value ends with the compare text
boolean validator – treats the value as a boolean (true/false) and routes it accordingly

If the condition is true, the data item goes to True Output; otherwise it goes to False Output. The component does all of this locally inside the dashboard, so no external services are called.

Inputs

Data Input: The Data object or list of Data objects to process.
Compare Value: The value to compare against (not used when the operator is boolean validator).
Key Name: The name of the key in the Data object(s) to check.
Comparison Operator: The operator to apply for comparing the values. boolean validator treats the value as a boolean.

Outputs

True Output: A list of Data objects that satisfied the condition.
False Output: A list of Data objects that did not satisfy the condition.

These outputs can be connected to other components, such as data storage, notifications, or further processing steps.

Usage Example

Add the component to your workflow.
Connect a data source (e.g., a database query or a file reader) to the Data Input field.
Set the Key Name to the field you want to test, such as status.
Choose a Comparison Operator. For instance, select equals.
Enter the Compare Value you want to match, e.g., approved.
Connect the True Output to a component that handles approved records (e.g., send an email).
Connect the False Output to a component that handles non‑approved records (e.g., log them).

Now, every time the workflow runs, records with status = approved will flow through the True path, while all others will go through the False path.

Data Filter – Filters data items based on a condition but keeps them in a single stream.
Data Splitter – Splits data into multiple streams based on a key value.
Data Aggregator – Combines multiple data streams into one.

Tips and Best Practices

Use boolean validator when the key holds values like true/false, yes/no, or 1/0 to avoid manual string comparisons.
Keep the Compare Value short and clear; complex logic should be handled in a separate component.
If you need to route based on multiple conditions, chain several Data Conditional Routers or use a Data Filter with multiple rules.
Test the component with a small sample of data first to confirm the routing logic before connecting it to production data sources.

Security Considerations

The component only processes data that is already in the dashboard; it does not send data outside the system.
Ensure that any data passed to the component does not contain sensitive personal information unless the dashboard’s overall security policies allow it.
If you connect the outputs to external services (e.g., email or API calls), make sure those services are secured and authenticated according to your organization’s standards.