Understanding 403 Error: Webhook Limitations and Auto-Dedupe Issues

Stephen F. · 2025-04-14T21:01:55.992982+00:00

I’m getting a 403 error for sending webhook data to a table with about 13K records that has auto-dedupe on w/ an error message of “Record limit reached for webhook”. Assuming this means there are 50k webhook attempts per source? Or is it table? I assumed the webhook would work up until the table reached its limit but guessing not. Additional clarity would be appreciated. Thanks

The "Record limit reached for webhook" error suggests you've hit a processing capacity limit for your webhook table. This limit is per workspace, not per source or table. Our system can process up to 10 records per second, with a maximum burst capacity of 20 records. To manage this, you may need to: 1. Create a new webhook table to continue processing 2. Modify your webhook sending rate to stay within limits 3. Consider batching noisier requests If you need more specific guidance on managing your webhook data or setting up auto-delete to maintain table efficiency, let me know.

Source: Import Data to Clay Using Webhooks

3 comments