Hi,
I am trying to use a webhook to trigger my flow. I wrote an application that will send request to the webhook. I have to send multiple requests (target multiple users) to the webhook. However, I am getting a HTTP status 429 response. I have tried manually queueing the requests (1 per second) but still getting the same response (429).
Is there any rate limit on webhooks?
Thanks,
Kenneth
Hi @jklm
There shouldn’t be any kind of rate limits that you’re hitting unless you’re throwing an insane number of requests at the webhook trigger - 1 per second definitely shouldn’t be an issue!
Have you tried testing with a simplified (single) request or from any other services like Postman or Request Bin to see if you get the same result?
I tried to send two consecutive requests using postman and here’s what I got:
Seems like it will only allow me to send another request to the same webhook after 27-ish seconds.
Thanks,
Kenneth
Hi Kenneth,
Is it the broadcast webhook trigger that you’re using? There are limits on how often those can be triggered to avoid spamming a large number of users (accidentally or otherwise!)
If you try with a normal receive a webhook trigger does it work for you?
Thanks,
Dan
Hi Dan,
I am using broadcast webhook trigger because I am trying to filter users by comparing a parameter passed to the webhook (user) and chat bot user’s id.
Can normal receive a webhook trigger also do this?
Thanks,
Kenneth
Hi Kenneth,
That wouldn’t be inherently possible using a standard webhook trigger, no. 
You could save your user ID’s to a separate database to query when the webhook is triggered, e.g. pull your existing user base from the users section on the website and then save them (and new users) to a Google Sheet so that when your flow is triggered you can search for a match.
Admittedly not quite as ideal but that hopefully helps 
