Unable to loop through array from webhook

[keystone]

I have a workflow that starts with a webhook trigger, receiving a POST request containing a JSON payload. The payload includes:

• An email field
• An agreements array

My goal is to iterate over the agreements array and send an email for each item. To achieve this, I configured a Loop step with a batch size equal to the length of the agreements array.

However, I encountered an issue: the Loop step does not expose the current iteration index in its output. This makes it impossible to determine which element of the original array is being processed in each iteration.

This limitation becomes problematic in the subsequent steps:

1. A Code step is used to download a PDF file from a presigned URL found in each agreement.
2. A Send Email step follows, which combines the original webhook data with the downloaded attachment to send an email.

Without access to the current index, there’s no reliable way to reference the correct agreement object in the original array, which breaks the intended logic of the workflow.

Expected Behavior:

The Loop step should expose the current iteration index (e.g., currentIndex) as part of its output, so it can be used in downstream nodes to correctly reference items in the original input array.

Any help is appreciated.

I’ve tried asking the assistant but it caused an error (see attachment)

[jabbson]

Hey @keystone hope all is well. Welcome to the community.

My understanding is that

• you get a request, which contains the email field and agreements array.
• for each agreement in the array you need to download the pdf specified in the agreement
• send the retrieved pdf to the email from the webhook.

So I assume the request body looks something like

{
  "email": "[email protected]",
  "agreements": [
    {"url": <url1>},
    {"url": <url2>},
    {"url": <url3>},
    ...
    ...
  ]
}

and you need to retrieve each pdf from each email and send it to the email address.

Please correct what I got wrong.

[jabbson]

Sorry could you try to answer again, the post got hidden for some reason.

[keystone]

Hi @jabbson that is correct, the request body looks similar to that.

[jabbson]

Try this then

[keystone]

Thank you very much @jabbson works a treat!

[jabbson]

Kindly mark the answer as solution and thank you!

Cheers!