Introduction to Sub-workflows
Sub-workflows are triggered by an action defined in a master workflow. Sub-workflows allow for more refined processing of a data point in a master workflow. This is particularly useful when dealing with arrays (lists) of data as a sub-workflow will run against each list item individually. Sub-workflows can also be nested infinitely.
For example, product variants are lists of data associated with one parent product. A master workflow might be configured to trigger when a product is updated, and have an Action in the master workflow that triggers a sub-workflow against each variant in that product.
Creating A Sub-workflow
From the edit screen on any Workflow, add an action to "Trigger a sub-workflow".
Options in the data selector vary by the type of data being processed by the master workflow.
Editing A Sub-workflow
Once the data to send is selected, the Action will contain a link to edit the Sub-workflow. Sub-workflows can only be accessed through this interface.
Conditions in Sub-workflows
Conditions are dependent on the data being sent by the master workflow. Nested items can now be targeted for each instance of that item.
Sub-workflows can be nested, allowing one sub-workflow to trigger another sub-workflow.