Auto-delete is available for webhook tables, but it's an Enterprise-only feature. [1]
To enable it: open your webhook table → click the table title → select "Enable auto-delete" → enable "Automatic row deletion".
If you're not on Enterprise, the main workaround is splitting your records across multiple tables to avoid the 50,000 record limit. When you hit the limit, you'll need to create a new webhook since the limit persists even after deleting rows. [2]
Yes, exactly. Since the 50,000 record limit persists even after deleting rows, you'll need to create new webhooks when you hit the limit. [1]
The recommended approach is splitting your records across multiple tables to avoid hitting the limit in the first place. This way you can distribute the load and cycle through different webhook endpoints as needed.
If you need any more help with managing webhooks or the record limits, please let me know. Would you like to provide more details about what you're trying to achieve so I can assist further?
There is no built-in auto-delete option for webhooks in Clay tables. This means data coming in via webhooks does not delete automatically. However, you can use workarounds such as staging tables, overwriting rows using a unique ID, or manual cleanup.
Actually, there is a built-in auto-delete option for webhook tables - it's just an Enterprise-only feature. [1]
Auto-delete works by automatically processing incoming webhook data, enriching it, then forwarding it to your destination before deleting the original entries from the table. [2] It kicks in when your table exceeds 5,000 rows and reviews every 60 seconds. [3]
If you're not on Enterprise, then yes - you'd need the workarounds you mentioned like splitting across multiple tables.
If you still need help with managing webhook data or exploring workarounds, I’m here to assist. Would you like to share more about your specific use case or what you’re trying to accomplish?
