DocumentationWorkflowsLogic and data
Repeat a list node
Processes a list in small groups. Connect the last step to Continue. Done starts only after every group has finished. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
7 min readUpdated
What this node does
Processes a list in small groups. Connect the last step to Continue. Done starts only after every group has finished.
Use Repeat a list as a clearly defined step in an anymize workflow.
- Processes 2 inputs.
- Provides 2 outputs for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Repeat a list 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
Repeat a list has one focused purpose. Its available settings appear when you select the node.
Settings
| Field | Meaning | Area |
|---|---|---|
| Entries per round | One entry processes the list step by step. Larger groups process several entries together. | Standard |
| Maximum rounds | Stops with a clear message if the list needs more rounds. Maximum 10000. | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| List | Configure this value in the node panel. | json |
| Continue | Configure this value in the node panel. | json |
| Output | Meaning | Type |
|---|---|---|
| Each group | Configure this value in the node panel. | json |
| Done | Configure this value in the node panel. | 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.