...
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 selected. Likewise, if the object contained an array, then “2.id” will select the third item’s “id” parameter.
Sub-Steps
Each Workflow Step has an optional Sub-steps section. This area is initially empty, but can be populated with sub-steps to create a Workflow within a Workflow. This Inner Workflow will be executed once for each item produced by the parent Step. For example, if the parent Step produces an array of five objects, then the Inner Workflow in the Sub-steps section will be executed five times, once for each object.
The Sub-steps section is executed after the parent call, but before the data is passed to the Conditions & Routes section.
The Sub-steps section is initially empty. The “add substep” button enables this area and navigates to a new screen which focuses exclusively on this inner Workflow. The “back to parent” button returns to the parent Step.
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.
In general, all the rules which apply to the normal Steps of a Workflow apply to Sub-steps.
One major difference is that a series of Sub-steps does not have an “Output,” but instead has a new field in its General Options field titled “Write output in parent scope.” This field substitutes for an Output area and allows the user to specify where to deposit the results in the parent's data object. These results will then be available to all subsequent steps as the Outer Workflow proceeds.
Each Inner Workflow can have, if needed, Sub-steps of is own, creating an Inner-Inner Workflow. There is no limit to how many Workflows deep this can go.
Workflows Executing Workflows
...