I'm seeing this error "You have reached the maximum number of columns allowed (100 total columns, 40 action columns). Please delete some columns before adding new ones." and I don't have anywhere near that – any thoughts?
This error occurs due to Clay's column limits: 100 total columns maximum with 40 action/enrichment columns per table. Even if you don't see that many columns visually, hidden columns, waterfall steps, and enrichment providers all count toward these limits.
To resolve this:
• Delete completed enrichment columns you no longer need
• Simplify waterfalls to use fewer steps or providers
• Split your workflow into multiple tables using the 'Send Table Data' action
The standard limit is 70 total columns with 30 action columns, but waterfalls raise the action limit to 40. [1]
Did that answer your question?
If you still need help managing your columns or understanding the limits, I’m here to assist. Would you like to provide more details about your table setup or the issue you’re facing?
Hey there Pasha thanks for reaching out, quick question are you adding a waterfall here to this table when you are seeing this message appear? What happens here is that when adding a waterfall to a Clay table, it will take into account both the existing columns in your table and the number of columns that are going to be added and if the total that you are going to add with your new waterfall would exceed the 40 column limit this is why the message would appear
Got it – so what's the best way to handle this? I can't delete individual enrichment columns (would have to delete the output) so do I:
Copy the column with verified emails to it's own column and delete the other waterfall columns?
Split into multiple tables?
What's best practice?
Sorry for the delay here, if you can't remove any of the existing columns or make changes so that waterfall that you're going to add has less columns to get below the limit here. And your next best bet would be to split this output into a second table here. You can use a Send Table data integration and send all the data over to a new table so then that way you'll have all the needed values to use as inputs for your next waterfall
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!
.png)