Within a workflow, there are certain fundamentals that apply to any step, whether it is an App Step, Mapper, or Utility Step.
Accessing Data
When it comes to accessing data, there are a few key things to know:
Each workflow step can access the data of each step before it, considering that the data will be the current data as of the last run of the step (in many cases, steps only run once so this is obvious, but in the case of iterations, this may be more complex).
When accessing data, you can reference the step number that correlates to the prior step you’re pulling from. For example:
.png "image(123).png")
Each number on the left matches the step number from the workflow itself.When configuring data within an array, you will need to map the array to an earlier step, as you can see here:
.png "image(125).png")
When selecting data for arguments within the array, you will see the parent step (“12 Get all products as a group” in the example above) at the top of the list. This is the iterated data that must be used to build the array. You will also see the same step again within the numerical step sequence, but that again will refer to the entire output - not the current iteration being used to build the array..png "image(126).png")
Output in Case of Failure
If a workflow step fails, you will see the details of the failure within the Output tab. This includes a cURL that you can use directly for debugging, and the raw response. For example:
.png "image(127).png")