.png){kind=logo}
Future Plans for Increasing Column Limit Above 100
Is there a plan to increase the number of allowed columns for csv upload in the future to >100? Might otherwise switch to Persana
Currently, our tables have a column limit of 70, not 100 as you mentioned. Of these, up to 30 can be action or integration columns. If you implement a waterfall, this integration column limit increases to 40. There's no immediate plan to increase this limit beyond 70 columns. If you're hitting the limit, you might consider deleting completed enrichment columns after retrieving the data, which can free up space for new ones. If you need further assistance with managing your columns, please let me know.
Bo (.··Hey Alexander, We're indeed planning to scale our infrastructure much more. I'm curious what you're hoping to achieve with more than a hundred columns. Can you tell us a little bit more about your use case?
Thanks Bo! Sure, I am exporting data from LinkedHelper and their minimum export comes with 108 columns
This means I always need to open their export first in GSheet, delete columns, export to csv and import to Clay. Across hundreds of campaigns this is a lot of effort
- Bo (.··
Got it. Thank you for your feedback - I've just sent this to our team. As a workaround, you might want to create a Python script with the help of AI tools like Cursor. This would allow you to automatically process your data and send the details through a webhook. I'd recommend exploring this direction. Example prompt: "I want to automatically export data from LinkedinHelper CSV that are always being saved in [location on your computer] with 108 columns, remove [columns 1, columns 2, etc], and then send all the results to this Clay webhook. Create a script that I can run from the click of one button in [your type of computer]."
Good idea, thanks so much Bo 🙏 please let me know when there is a planned change of the import restrictions
- Bo (.··
Will do, Alexander! Let me know if I can do anything else!!!! :)