Detecção de Spam em E-mails com IA e Roteamento para Suporte
Este fluxo de trabalho com IA classifica automaticamente e-mails recebidos como spam ou não, e encaminha de forma inteligente mensagens legítimas para um assist...
5 min read
The Conditional Router is a flow component designed to direct the flow of messages based on customizable text comparison logic. This makes it a powerful tool for branching processes, enabling dynamic decision-making within your AI workflows.
What the Component Does
At its core, the Conditional Router examines a piece of input text and compares it against a specified match value. Based on the result of this comparison (using a chosen operator, such as “equals,” “contains,” or “is empty”), the message is routed down one of two possible paths: the True Route or the False Route. This allows your workflow to automatically handle different scenarios based on message content or structure.
Inputs
The Conditional Router accepts several parameters to configure its behavior:
| Input Name | Type | Description | Required | Advanced |
|---|---|---|---|---|
| Input Text | String | The primary text input for the operation. | No | No |
| Match Text | String | The text input to compare against. | No | No |
| Operator | String | The operator for comparing the texts (see below). | No | Yes |
| Case Sensitive | Boolean | Whether the comparison should be case sensitive. | No | Yes |
| Message | String | The message object to pass through on either route. | No | No |
Available Operators:
equalsnot equalscontainsstarts withends withis emptyis not emptyis_urlis_emailis_number
This wide choice of operators enables sophisticated routing logic, such as matching by substring, checking for empty inputs, or validating the format of a URL/email/number.
Outputs
The component provides two output paths:
- True Route: Activated when the comparison evaluates to true. The original message is passed through this output.
- False Route: Activated when the comparison evaluates to false. The original message is passed through this output.
Both outputs are of type “Message,” ensuring compatibility with downstream components in your workflow.
Use Cases and Benefits
The Conditional Router is especially useful for:
- Branching Logic: Directing messages to different components or actions based on their content.
- Validation: Filtering messages that meet specific text criteria (e.g., emails, URLs, non-empty fields).
- Personalization: Customizing the flow of user interactions depending on user input.
- Automation: Automating responses or actions for certain keyword triggers or message patterns.
By integrating this component into your workflow, you can build highly responsive and adaptable AI processes that react intelligently to a wide range of input scenarios.