Hi, I'm pulling in data from a webhook into a table, then do a column dedup. I noticed that the 1st step has 23251 rows, while the 2nd step has 8864 after dedup. So for Clay's 50k rows limit, is it based off the 1st step or the 2nd step?
The 50k limit applies to your webhook table (the first step with 23,251 rows). Webhook tables have a strict 50,000 record limit, and this counts all submissions to the webhook regardless of what happens in downstream steps like deduplication. [1]
So even though your second step only shows 8,864 rows after dedup, the webhook itself has already received and stored 23,251 records, which is what counts toward the limit.
Once you hit 50,000 submissions to a webhook, you'll need to create a new webhook to continue receiving data - the limit persists even after deleting rows. [2]
Was that helpful?
there's no way to "clear" the clay webhook data?
Unfortunately, there's no way to manually clear or reset webhook data to free up space under the 50k limit. The webhook submission limit persists even after deleting rows from your table. [1]
Your only options are:
Create a new webhook - Once you hit 50k submissions, you'll need to set up a fresh webhook URL to continue receiving data. [2]
Enable auto-delete (Enterprise only) - If you're on Enterprise, you can set up passthrough tables that automatically delete rows after processing, allowing continuous data flow without hitting the limit. [3]
The 50k limit counts all submissions ever made to that specific webhook, not just current rows in your table.
Did that answer your question?
If you need any more help understanding the webhook data limits or options, I’m here to assist. Would you like to share more about what you’re trying to achieve with your webhook data?
is there a slack or webhook that alerts us when a table is nearning 50k?
Clay doesn't have specific alerts for the 50k table row limit, but there are some related notification systems:
For workspace-wide limits: You'll get notifications when approaching your total workspace row limit across all tables.
For credit limits: Clay sends notifications when workbook credit spend limits are approached or hit - these go to workspace admins and users added to specific workbooks via email and in-product UI. [1]
For expensive runs: Clay shows warnings for runs that cost more than 10% of your monthly credits or over 50k credits. [2]
But for individual table row limits approaching 50k, there's no built-in alert system currently available.
Is that what you were looking for?
If you still need help with webhook data limits or notifications, I’m here to assist. Would you like to provide more details about what you’re trying to resolve or understand?
Yes! The Enterprise plan's auto-delete feature works specifically for webhook tables and can help manage the 50k limit. [1]
Auto-delete automatically processes incoming data, enriches it, then deletes the original rows from your table after successful processing. This creates a "passthrough" system that keeps your table under the limit while continuously handling new data. [2]
To enable it:
Open your webhook table
Click the table title and select "Enable auto-delete"
Enable "Automatic row deletion"
Optionally enable "Success field check" to confirm columns run successfully before deletion [3]
However, the 50k webhook submission limit still applies - auto-delete helps manage table rows but doesn't reset the total submission count to your webhook URL. Once you hit 50k total submissions, you'd still need a new webhook.
Before we explore other options, have you tried using Sculptor? It's our built-in AI tool in the top-right corner that can help set up automations and workflows - it might have additional solutions for your specific setup.
If you need any further assistance with managing your webhook data or using Sculptor, I’m here to help. Would you like to share more about what you’re trying to achieve or any specific challenges you’re facing?
