DocumentationWorkflowsLogic and data
Condition node
Branches the workflow into two paths: if the condition is true (e.g. “score > 50”), the workflow continues along the top, otherwise along the bottom. Templates like {{ input.score > 50 }} are allowed. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
7 min readUpdated
What this node does
Branches the workflow into two paths: if the condition is true (e.g. “score > 50”), the workflow continues along the top, otherwise along the bottom. Templates like {{ input.score > 50 }} are allowed.
Use Condition as a clearly defined step in an anymize workflow.
- Processes one input.
- Provides 2 outputs for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Condition from the node catalog.
- 02Complete the required fields and map values from previous steps.
- 03Run the node with a small test record and inspect its output.
- 04Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
Condition has one focused purpose. Its available settings appear when you select the node.
Settings
| Field | Meaning | Area |
|---|---|---|
| Rules | Checks every entry using the imported comparisons. All values keep their data type. | Standard |
| Condition | Configure this value in the node panel. | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| value | Value the condition is checked against. | any |
| Output | Meaning | Type |
|---|---|---|
| true | When the condition is true. | any |
| false | When the condition is false. | any |
Example and test run
Score gate: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"score": 73,
"threshold": 50
}Access and security
Before activation, review which data enters this step and what its output contains.
Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.