...
When the workflow is executed each condition is evaluated against the user-given data, from top to bottom, in order. One Once a matching condition is found the Workflow immediately proceeds to the indicated step.
...
Once a Step’s Iteration Variable is changed from “omitted,” each Input across all sections gains access to the “iteration” data type. If selected, this input will be supplied with data from the iteration cycle.
...
In the case of a more complicated JSON structure (ex: [ { id: 123}, {id : 321 } ] ), the entire object will be provided to the variable. If only part of the structure is required, it can be accessed using the same semantics used to navigate JSON trees elsewhere. In the above example “{id: 123}” will be passed to the input by default, but if the input is configured with “id”, then only the value “123” will be passed inselected. Likewise, if the object contained an array, then “2.id” will select the third item’s “id” parameter.
...
The Sub-step edit screen is very similar to the normal Workflow Step editing area. You can add individual Sub-steps, each invoking an endpoint of a configured API service, connected by Conditions & Routes sections and utilizing data provided by previous Steps from both inside and outside the Sub-step area. It works exactly like a complete Workflow, only self-contained and dedicated to manipulating the data result of a parent Step.
...