Today the rate limit for Webhooks (a type of System trigger) is 5 requests/second. We are aiming to significantly increase this to 50+ requests/second.
6. Delivered
Increase Webhook Rate Limit
+2
+2We are facing a very similar challenge on our side as well. The current webhook rate limit feels too restrictive for real enterprise scenarios, especially for alerts, approvals, and other event-driven integrations where one webhook may be triggered per user, per request, or per system event.
In some Python-driven use cases, batching may be possible, but for systems like SAP, Coupa, and similar platforms, changing the source logic to send everything in one bulk payload is often not practical. We already saw simple scenarios fail because of the current limit.
It would be much more scalable if Moveworks could support a higher rate limit for single-event webhooks and handle scale through queueing and asynchronous backend processing. Bulk payload support is useful, but it should ideally be an optimization, not the only workable model.
Sign up
Already have an account? Login
If you're a Moveworks customer, you can click the SSO button below to login-even if it's your first time. Everyone else can use email or click create an account above to register.
LOGIN WITH MYMOVEWORKS SSO PARTNERS WITH SSO LOGINor
Login or create an account
If you're a Moveworks customer, you can click the SSO button below to login-even if it's your first time. Everyone else can use email or click create an account above to register.
LOGIN WITH MYMOVEWORKS SSO PARTNERS WITH SSO LOGINor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.