Automation for Creating New Table When Clay Table is Full

John T. · 2026-01-09T07:36:15.014Z

i wanna create an automation whereby when a clay table is almost full (let's say 45000 rows, it automatically creates a new table). is there a way to do this?

Automation for Creating New Table When Clay Table is Full | Clay

7 comments

· Sorted by Oldest

Clay Support
APP
·
·
There isn't a built-in automation to automatically create new tables when approaching the 50,000 row limit.
However, if you're on the Enterprise plan, you can use Passthrough Tables which automatically handle the row limit by processing data, enriching it, then forwarding it to a destination and deleting the original entries. [1] This keeps your table manageable while continuously processing new data. [2]
For non-Enterprise users, you'll need to manually split data into smaller tables or monitor your row count and create new tables as needed.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you need any more help with setting up your automation or managing your tables, please let me know. Would you like to share more details about what you're trying to achieve so I can assist further?
Matt S.
·
·
You can have one column (some sort of function) that auto counts the row number - when it reaches to 50k, it's automatically pushing a webhook that goes to n8n, and changes all the api end points from your table 1 to table 2 (you created in advance) and then it keeps going and going like this 🙂 it's just an idea but i'd ask claude code about this
Clay Support
APP
·
·
That's a creative approach! Clay doesn't have a built-in row counter function, but you could potentially set up something similar using webhooks and external automation tools like n8n. [1]
You'd need to track row counts externally since Clay tables don't expose current row counts through their webhook system. The webhook URLs are static per table, so you'd handle the endpoint switching logic in n8n rather than within Clay itself. [2]
Before diving into custom coding, I'd recommend trying Sculptor first - our built-in AI tool in the top-right corner. It might help you brainstorm or set up parts of this automation workflow more easily. Give it a shot and let me know if it helps with your setup!
If Sculptor doesn't cover what you need, then yeah, Claude or another coding assistant could definitely help you build the n8n logic for tracking counts and switching endpoints.
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need help with setting up your automation or have more questions about using Sculptor or webhooks, I’m here to assist. Would you like to provide more details about your setup or any specific challenges you’re facing?

Clay Support
APP
·
·
There isn't a built-in automation to automatically create new tables when approaching the 50,000 row limit.
However, if you're on the Enterprise plan, you can use Passthrough Tables which automatically handle the row limit by processing data, enriching it, then forwarding it to a destination and deleting the original entries. [1] This keeps your table manageable while continuously processing new data. [2]
For non-Enterprise users, you'll need to manually split data into smaller tables or monitor your row count and create new tables as needed.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you need any more help with setting up your automation or managing your tables, please let me know. Would you like to share more details about what you're trying to achieve so I can assist further?
Matt S.
·
·
You can have one column (some sort of function) that auto counts the row number - when it reaches to 50k, it's automatically pushing a webhook that goes to n8n, and changes all the api end points from your table 1 to table 2 (you created in advance) and then it keeps going and going like this 🙂 it's just an idea but i'd ask claude code about this
Clay Support
APP
·
·
That's a creative approach! Clay doesn't have a built-in row counter function, but you could potentially set up something similar using webhooks and external automation tools like n8n. [1]
You'd need to track row counts externally since Clay tables don't expose current row counts through their webhook system. The webhook URLs are static per table, so you'd handle the endpoint switching logic in n8n rather than within Clay itself. [2]
Before diving into custom coding, I'd recommend trying Sculptor first - our built-in AI tool in the top-right corner. It might help you brainstorm or set up parts of this automation workflow more easily. Give it a shot and let me know if it helps with your setup!
If Sculptor doesn't cover what you need, then yeah, Claude or another coding assistant could definitely help you build the n8n logic for tracking counts and switching endpoints.
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need help with setting up your automation or have more questions about using Sculptor or webhooks, I’m here to assist. Would you like to provide more details about your setup or any specific challenges you’re facing?