How can I aggregate multiple operation into a single JSON response for a webhook in Make?

Hi,
I’m building a scenario where:

  1. The scenario starts with a webhook (triggered by Prontoform).
  2. I use a JSON module to parse a list of statuses from Prontoform.
  3. I fetch orders via HTTP, filtered by these statuses.
  4. I use an iterator because I can have more than 1000 orders.
  5. For each order, I make another HTTP call to fetch contacts by ID.
  6. I use an iterator again to handle all results.
  7. I use a Set Multiple Variables module to select only the fields I need.
  8. I use an Array Aggregator to gather all the results.
  9. I build a JSON with the aggregated results.
  10. I send a Webhook Response back to Prontoform.

Problem:
Even though I’m using the Array Aggregator (step 8), the Webhook Response at the end still returns multiple responses (one for each operation/bundle).
Prontoform only uses the first operation, so only the first batch of data is transferred.

What I need:
I want to consolidate all data from the different iterations and return a single JSON response to the webhook, so that Prontoform gets all the data at once (one operation, one JSON).

What I tried:

  • Placing the Array Aggregator after “Set Multiple Variables” to gather all bundles
  • Ensuring the Webhook Response is only connected to the JSON created by the aggregator
  • Changed the “Maximum number of results” in Webhook trigger, but I still get more than one operation in the run output

What am I missing?
How can I make sure the Webhook Response returns only one operation containing all the aggregated data?

Thanks for any help,
Salvatore

Ps: what i want at the end is to have only one operation in the web hook response instead of thousand of operation for example in this photo what i don’t want:


You see that the web hook is divided in 2 operation? i need to be only one with only one json that contain everything inside, all the operation in one single json

Hey there,

usually this issue is because you are aggregating the wrong module. You always aggregate the module producing the extra bundles.