What is the internal rate limit for webhooks in Pabbly Connect?

sven-bo

Member
Your Workflow URL
https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTY5MDYzMjA0MzM1MjY0NTUzNjUxMzci_pc
Your Task History ID
IjU3NjUwNTZiMDYzMDA0MzE1MjZkNTUzNzUxM2E1MTZiNTQzNzBmMzAi_pc
Consent to Access & Modify
I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.
My webhook URL has been exposed and is now being triggered many times per second. I noticed that this doesn’t use up my quota, since the workflow is filtered and nothing actually runs, so I’m not worried about that part.

I’m just curious:
  • Does Pabbly Connect apply any internal rate limit on webhook requests?
  • For example, is there a maximum number of requests per second/minute that Pabbly accepts on a single webhook URL?
  • If thousands of requests per second are sent, will they all be accepted, queued, or are some dropped automatically?
Thanks for clarifying!
 

Preeti Paryani

Well-known member
Staff member
Hello @sven-bo,

One way to prevent a workflow from being triggered multiple times is to create a new webhook URL by cloning your workflow. You can then disable the current workflow and add the new workflow’s webhook URL in the trigger application. Since every workflow has a unique webhook URL, this approach helps stop multiple triggers.

Regarding rate limits, please note that we have an internal limit of 400 webhook responses per minute. I have attached a forum thread below that explains this in more detail and should help you understand the process better.

 
Top