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

Workaround for 50K Rows Limit in Data Import Process | Clay

Workaround for 50K Rows Limit in Data Import Process

·Apr 20, 2025 11:31 PM·

Is there a workaround on the 50K rows limit? I used "write to" instead of "import" but it went error as the destination table almost to reach 50K rows.

4 comments

· Sorted by Oldest

Channeled
APP
·
·
Unfortunately, there isn't a direct workaround for the 50K rows limit when using the "write to table" feature. This limitation is part of the constraints of the feature. However, you might consider splitting your data across multiple tables to manage larger datasets. To better assist you, could you provide more details about your specific use case and the type of data you're trying to write to the table? This information would help in suggesting potential alternative approaches within Clay's capabilities.
Sources: Write to Other Table | Documentation | Clay University Write to Other Table | Documentation | Clay University
Lemuel C.
·
·
but the challenge on splitting, I can only select 1 exclusion table.
Bo (.
·
·
Unfortunately, there’s no way to bypass the 50K row limit at the moment. If you’re working across multiple tables, try using a Lookup step to reference the second table with up to 50K rows. Let me know if you need help setting that up.
Channeled
APP
·
·