Allows to define a list of tasks (flows) that are processed sequentially. A task defines whether it has ended or not by sending the message to a return-node.

Inputs

Name string

Set a custom name for your node.

Mode string

Select what you want to loop through your tasks with. You can work through your tasks once with the whole message object (default) or do all tasks for each value of a collection.

Collection collection

If do task for each value: Select the collection you want to iterate.

Send string

If do task for each value: Select if you want the key / value / key-value pair from the collection.

Tasks array

Each task will create a separate output for the node, in which you can handle the task.

Done output boolean

Create an output which will continue the flow after doing all tasks.

Outputs

1. Task outputs

   payload string

   Each task will have an output.

2. Done output (optional)

   payload string

   The output after the task list is done. Can be deactivated with the "Done output" option.

Details

A do-node with two outputs (one task and the done-output) is a very simple way to define a loop. The task (flow) thereby needs to either return continue if the loop has not yet ended or next resp. done in case the loop shall end.