Webhook tables in Clay are limited to 50,000 submissions. [1] This limit persists even after deleting rows, so once you hit 50,000 submissions, you'll need to create a new webhook table to continue receiving data.
If you're on the Enterprise plan, you can enable auto-delete (passthrough tables) to automatically process and delete rows, which allows unlimited webhook submissions.
For webhook request rates, Clay has a throughput limit of 10 requests per second. [1]
For packet size, webhooks can handle up to 200KB per request since they're action columns. [2] If you need to send larger payloads, you can use field-path filters to reduce the data size.
These limits help ensure stable performance across all webhook integrations.
If you need any more help with webhook limits or have other questions, I’m here to assist. Would you like to provide more details about what you’re trying to achieve with webhooks?
