We have a special situation and are curious if there is a workaround to reduce the amount of zap runs.
An external party sends out a webhook, with a lot of information about a deal.
Zapier does trigger on this webhook. 95% of the time it's only a 1 time trigger, but sometimes this deal is updated continously in the first 60 minutes. This can be as much as like 50 times.
If this is the case (like say 50 times) actually only the last trigger contains all the info we need.
We could trigger this zap for 50 times and update the deal with all the new information, but this is somehow a overload on information where we know the first 49 times that this is somehow a waste of using of the resources.
We know there is an option to set a queue for zap runs if the other has been passed, but this is only postpone all the runs after the first one - and is not ideal for this job.
Is there a way to hold this first run - wait for about an hour - see if there are any other webhooks in the queue (that are filtered with the same DEAL ID?) - and then only run the last webhook and kill all the others?
Is there a way to use the 'Queue Zap' and skip some other Zap runs with some filters?
- Beginner
- 1 reply
+14
- Certified Zapier Expert
- 24153 replies
-
4 September 2023
Hi
Good question.
What data point in the data payload indicates the Deal has done being updated?
If there is a data point, then you can use a Filter as Step 2.
Otherwise, you’d have to log all these webhook requests to check against. (e.g. GSheet, Airtable)
- Beginner
- 1 reply
-
5 September 2023
Hi
I thought maybe there was a zapier function for this, but as I can understand of your reaction this function does not exist.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.