Unexpected multiple runs for a single webhook

Your Zap history shows multiple successful runs for what you expected to be one single event. For example, you sent one webhook request, but 10 separate runs appeared in your Zap history, all triggered at the same time.

Causes

This behavior is caused by the way Zapier processes an array of objects. When the Webhooks by Zapier trigger receives an array (line items), it automatically treats each object inside that array as a separate line item. Zapier then creates a separate Zap run for each one (a process called "forking"), and runs the subsequent action steps individually for every line item. This is a feature designed to help you process a list of data without needing to send multiple individual requests.

Learn more about sending an array of objects with webhooks.

How to fix it

Option 1: Process as a single object

If you want the entire array to be treated as a single piece of data (i.e., you only want your Zap to run once), adjust the webhook's data format, if the app allows it. Instead of sending the array as the top-level payload, nest it inside another object within a key. This ensures the Zapier trigger reads only one top-level object. 

Option 2: Create a private app

If you need more control over how data is received and handled, consider building a private app using Zapier’s Developer Platform.

Note

The Zapier Support team is able to provide basic troubleshooting for Webhooks by Zapier and API Request actions, but they cannot troubleshoot the API you use.