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
Clay Cup

Powered by Tightknit

Automating Row Deletion in Clay When Exceeding 50k Limit | Clay

Automating Row Deletion in Clay When Exceeding 50k Limit

·Nov 06, 2024 04:10 PM·

Hello, wondering if there a is method to automatically remove the oldest rows from a table once it has reached the 50k row limit. Currently just removing the oldest manually but figured there should be some mechanism in Clay to overwrite/delete the oldest. Thanks!

6 comments

· Sorted by Oldest

Mark L.
·
·
Hello Dragan. We do have a feature that can auto-delete rows, designed for high-volume webhooks. However, this is available only on the Enterprise plan (https://www.clay.com/pricing). That said, when the limit is hit, Clay should return a 403 response, "Record limit reached". You would need to use that as signal to create/swap to a new webhook endpoint. I recognize this isn't ideal today, but I've made sure we have this use case captured for future product improvements around notifications/alerting, more generally.
Dragan K.
·
·
The volume is not due to a webhook, i write to the table from a zap, so I was looking for something similar to a column that has a delete function if a formula evals to true from within clay, but seems like I'll just have to purge the table on a schedule manually.
Mark L.
·
·
Ah, I understand. There are no conditional-delete abilities within Clay. I like the idea, though, that could be powerful. Please let me know of other questions!
Dragan K.
·
·
Just to maybe plant the seed, allow for a table setting that allows overwrites for certain tables, but off by default. Not really a question though
Mark L.
·
·
Welcome feedback, though! Thanks for taking the time to share and elaborate on the use case.
Channeled
APP
·
·
Hi Dragan K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: