Home

Clay Announcements
Clay Support
Discuss Anything
Feedback & Requests
GTM Career Advice
Introduce Yourself
Member Spotlight
Share Content and Events
Share Full-time Jobs
Share Part Time Jobs
Share Tables, Tools, and Workflows

Community Guidelines

Explore Events
Learn Clay here
Clay Cup

Powered by Tightknit

Webhook Limitations: Discrepancies in Row Transfer Explained | Clay

Webhook Limitations: Discrepancies in Row Transfer Explained

·Nov 07, 2025 09:52 PM·

Are there any limitation to webhook as a source? I'm seeing 3.5k rows received through webhook but only 2k rows in the downstream table. No filters

3 comments

· Sorted by Oldest

Clay Support
APP
·
·
Yes, webhooks have several limitations that could explain your issue:
Key webhook limitations:
50,000 submission limit per webhook source (persists even after deleting rows) [1]
Rate limit: 10 records per second, with burst capacity of 20 records [2]
Payload size limit: 100KB per payload
Table row limit: 50,000 rows total per table (includes all rows, even deleted ones)
The discrepancy between 3.5k received and 2k in your table could be due to rate limiting if data was sent too quickly, or if you've hit the webhook submission limit. When limits are exceeded, new records cannot be processed.
To resolve this, you may need to create a new webhook source or split your data across multiple tables.
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need help understanding the webhook limitations or resolving the row discrepancy, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any other issues you’re encountering?