Skip to content
Nappai Documentation

Conditional Router

The Conditional Router is a simple tool that looks at a piece of text and decides which way to send a message.
You give it a text to check, a text to compare it with, and choose how the comparison should work (equals, contains, starts with, etc.).
If the comparison is true, the message goes to the True Route; otherwise it goes to the False Route.

How it Works

The component takes the Input Text and compares it to the Match Text using the chosen Operator.
You can decide whether the comparison cares about capital letters with the Case Sensitive toggle.
If the comparison returns true, the component forwards the Message to the True Route output.
If it returns false, the message is sent to the False Route output.
All of this happens inside the dashboard – no external services are called.

Inputs

  • Case Sensitive: If true, the comparison will be case sensitive.
  • Input Text: The primary text input for the operation.
  • Match Text: The text input to compare against.
  • Message: The message to pass through either route.
  • Operator: The operator to apply for comparing the texts.

Outputs

  • True Route: A Message that is sent when the comparison is true.
  • False Route: A Message that is sent when the comparison is false.

Usage Example

Imagine you have a list of customer support tickets and you want to send tickets that mention “refund” to a special team.

  1. Input Text – the ticket description.
  2. Match Text – the word “refund”.
  3. Operator – choose contains.
  4. Case Sensitive – leave unchecked so “Refund” or “refund” both match.
  5. Message – the whole ticket object.

If the ticket description contains “refund”, the ticket goes to the True Route (e.g., a “Refund Team” queue).
Otherwise it goes to the False Route (e.g., the regular support queue).

  • Text Matcher – compares two texts and returns a boolean.
  • Message Router – routes messages based on a condition but uses a single boolean input.
  • Text Splitter – splits a long text into parts that can then be routed individually.

Tips and Best Practices

  • Use is empty to check for blank inputs before routing.
  • Keep Case Sensitive off unless you need exact capitalization.
  • Combine this component with a Text Splitter to route parts of a long message separately.
  • Test the logic with sample texts before connecting to live data.

Security Considerations

The component only processes text locally; it does not send data outside the dashboard.
Ensure that any sensitive information in the Message is handled according to your organization’s data‑privacy policies.