Process a list by calling a child Flow for each item.

This function does not return any outputs - use it when you want to take action for each item in a list but don’t need any information back.  If you do need output values from your Flow, one of the other functions in the List category should work for you.

To use this function, first build the child Flow that you will use to process each item – to be invoked once for each item in the list. Define the inputs for the Flow on that event card. Typically you would include one input for the item of the list, i.e. if the list is a list of text then one of the inputs should be text. You can also include other inputs, whatever your Flow needs. If you need to know the position of the current item within the list, use the “Index” field from the Context section of the child Flow card. Then build the rest of the child Flow. No need for a Return card because no value gets returned to the For Each card. Save the child Flow and turn it on.

Now go back to the For Each card,  input the list you want to use, and then select the Flow you just built. The inputs will auto-populate, then you can map data into them. To map an input to accept each item of the list, click in that field and you will see a dropdown that includes item - select that. Or if your list is a list of objects, you may also see the schema of the object, i.e. the keys that it contains, and you can choose to have your child Flow to accept those as inputs. In addition, you can drag in outputs from previous cards in the Flow, in which case the same value will be used for each item in this list.

Input Fields

  • list: The list to operate on
  • flow:  The child Flow that will be called once for each item in the list
  • with the following values (dynamically generated):  The inputs defined by the child Flow - these will populate when you select the child Flow using the Choose Flow dialog
  • concurrency:  The number of items in the list to process in parallel.  If it is important that the items are processed in sequence, use 1.  Otherwise a higher number like 5 or 10 will cause your Flow to complete sooner.

Output Fields

  • (none)