Condition component (AI Flowi Workflow)
Condition routes Data objects using a condition applied to a specified key, including a boolean-validation option. It fits between a step that supplies structured data and the destinations chosen by that key-based check.
Condition is documented in the catalogue; not production-tested by Ai Flowi.
By Ai Flowi · Published
Where Condition fits
The Condition entry in the catalogue exported 9 October 2026 for version 1.9.2 marks all four inputs optional. For a useful key comparison, still choose your data source, key, operator and comparison value deliberately; optional metadata does not specify the behaviour of a blank configuration.
Inputs
Condition input names, types and required flags below come from the component catalogue. For Condition, “Not listed in export” means no accepted-connection list was supplied; it is not a claim that every type is supported.
On small screens, scroll either Condition table sideways to read every column.
| Name | Type | Required | Accepted input types | Plain explanation |
|---|---|---|---|---|
compare_value | str | No | Message | Text value used for the comparison; can come from a Message. |
data_input | other | No | Data, JSON | Data or JSON object connection to evaluate. |
key_name | str | No | Message | Name of the key to check in the supplied data. Nested-path syntax is not listed. |
operator | str | No | Not listed in export | Choose equals, not equals, contains, starts with, ends with, or boolean validator. |
Outputs
Condition exposes true_output (True Output) and false_output (False Output), both typed JSON. Connect those to JSON-compatible destinations. Unlike the verification and HTTP-method router descriptions, this entry does not explicitly promise preservation of every field.
| Name | Display name | Type |
|---|---|---|
true_output | True Output | JSON |
false_output | False Output | JSON |
When to use Condition
Use Condition when a decision is attached to a named data key, such as a status supplied by an earlier step. JSON Operations performs operations on a JSON object; Condition supplies the two routing outputs for a key-based rule.
When not to use Condition
When you are comparing an entire text message, If-Else documents required input_text and match_text fields and Message outputs. When upstream logic already supplies a complete verification result, Verification Router documents Verified and Rejected routes without removing or changing fields.
example configuration, not a recorded test
data_input: [connect a Data or JSON object]
key_name: status
operator: equals
compare_value: readyThe bracketed line represents a connection, not a literal string to pass as data. In this illustrative setup, status is a key you supply upstream and ready is its comparison value; neither is an additional component input. Verify the actual object and both branches in the editor.
Limitations
- The boolean validator option is named, but accepted boolean representations are not specified. Do not assume the strings “true” and “false” are handled like JSON booleans.
- Missing-key, null-value, list and nested-object behaviour are not defined in the export. Inspect representative input objects rather than treating those cases as established results.
- The listed operators do not include regex or numeric comparisons. If-Else lists those operator names, but its Message interface differs; select a component by the data contract as well as the rule.
Related components
If-Else · Verification Router · HTTP Method Router · JSON Operations
Node runs and usage
Plans: Go from USD8/month billed yearly (USD10 monthly), Plus from USD16 (USD20 monthly), Pro 100 from USD80 (USD100 monthly), Pro 200 from USD160 (USD200 monthly) and Pro 500 from USD400 (USD500 monthly), with 5,000 to 250,000 Flowi Tokens/month and top-ups; 1 token per node run; third-party API and model usage is not included.
Include Condition and the actions reached through its JSON outputs in your node-run estimate; any third-party API or model calls in those actions are billed outside the included Workflow usage. Review pricing for Condition.
Related: Production systems in AI: facts, rules and conflict resolution.