DocumentationWorkflowsLogic and data
Split Out node
Turn a list held in one field into separate items, one item per list element. The inverse of Aggregate. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
7 min readUpdated
What this node does
Turn a list held in one field into separate items, one item per list element. The inverse of Aggregate.
Use Split Out 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
- 01Open a workflow and add Split Out 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
Split Out has one focused purpose. Its available settings appear when you select the node.
Settings
| Field | Meaning | Area |
|---|---|---|
| Field to split | Configure this value in the node panel. | Standard |
| Other fields | Choices: List element only, Carry all other fields, Keep selected fields | Standard |
| Import version | Configure this value in the node panel. | Standard |
| Fields to keep | Enter the extra field names, separated by commas. | Standard |
| New field names | Optionally enter one new name per split list, in the same order and separated by commas. | Standard |
| Treat dots as part of the name | Reads customer.items as one complete field name. When off, it reads items inside customer. | Standard |
| Keep files | Carries attached files into each new item. | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | Receives the complete result from the previous step. | JSON |
| Output | Meaning | Type |
|---|---|---|
| Standard | Makes the result available to the next step as JSON. | JSON |
Example and test run
Test-run example: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"input": "value"
}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.