Open app

DocumentationWorkflowsLogic and data

Multi-condition node

Routes data through the first matching condition to a named output. The fallback runs when none match. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

7 min readUpdated

What this node does

Routes data through the first matching condition to a named output. The fallback runs when none match.

Use Multi-condition as a clearly defined step in an anymize workflow.

  • Processes one input.
  • Provides one output for following steps.
  • Runs as a regular step in the flow.

Set up the node

  1. 01Open a workflow and add Multi-condition from the node catalog.
  2. 02Complete the required fields and map values from previous steps.
  3. 03Run the node with a small test record and inspect its output.
  4. 04Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

Multi-condition has one focused purpose. Its available settings appear when you select the node.

Settings

FieldMeaningArea
BranchesOne named output per condition. The first match wins.Standard
Fallback outputUsed when no condition matches.Standard

Inputs and outputs

InputMeaningType
valueInput evaluated by the conditions.any
OutputMeaningType
StandardMakes the result available to the next step as JSON.JSON

Example and test run

Route events by type: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "status": "offen",
  "type": "invoice"
}

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.

Related articles