Changing between Iterator results

[hugohamelcom]

Your Task History ID

IjU3NjYwNTZlMDYzNzA0MzU1MjZiNTUzNTUxMzQi_pc

Hi,
Is there a way to cycle through iterator results to get a range of data that fit all our use cases?
Right now I am only able to see one set of data and that makes it impossible to complete the automation as not all set of data have the same JSON structure.
Thanks!

 

[Luv]

Hey @hugohamelcom

In the Iterator Module, the response displays only the first array and its key-value pairs from the entered JSON. To meet your use case, you will need to use different JSONs.

Let us know if you need any further clarification.

 

[hugohamelcom]

Hey @Luv, that is exactly the issue, if the response contain 100+ arrays with different format but only a few have all the values necessary to complete the automation, how can I access that exact array?
Would it be possible to add a way to select a specific array in the iterator module to be able to get all the values needed?
Thanks!

 

[Deleted member 9923]

Hello @hugohamelcom ,

In the iterator module, the response will only contain one key-value pair at a time. If you need to retrieve more key-value pairs, you would need to iterate again. You can modify the JSON accordingly and run the iterator multiple times to gather all the required values. Each iteration will return first key-value pair, so you would have to repeat the process to get the full set of data.

 

[hugohamelcom]

Hey @MukeshR, why not just add a "navigation" to the iterator? Because if I add a temporary transformed JSON and then remove it I won't be able to access it in the iterator anymore, so when I will save the new value it will break all the other modules and say the values doesn't exist.

 

[ArshilAhmad]

Could you please create a short screen recording showing the issue you're encountering? Also, share the workflow URL where this issue is occurring.

 

[hugohamelcom]

Maybe that helps: https://www.loom.com/share/d3e661153cb7415baebc8e0827cd9c1e?sid=02ef5d3b-9f4b-4cc5-9828-2d96bcaac3c5

 

[Preeti Paryani]

Hello @hugohamelcom,

Upon reviewing your use case, it seems that each object in the API response has a different structure. Currently, the iterator can only map the first object of the array. Since the first object doesn’t contain the required information, your use case doesn’t appear to be achievable at this time.

However, if you can modify the API response so that the first object in the array includes all the necessary fields for processing, you could then add filters to your workflow based on this object. This would allow the automation to function correctly.