Hello - Looking for solutions to work with the cell size limit. I have an application that needs the entire JSON enrichment of a contact exported - in its complete format. For most profiles the JSON, when converted to text and added to a column, is too large - above the 8kb limit. Using stringify to break it into multiple cells and then putting them back together at integration has caused issues, creating a word doc of the multiple fields has worked but is adding more to my workflow than desired with my endpoint, and adding the full JSON as an / inserted column has an error ever time. Appreciate any help & ideas! 🙂
For large JSON exports exceeding the 8KB limit, try these approaches:
Use field paths to extract specific data: Instead of the full JSON, use dot notation like data.contact.email to pull only needed fields from your enrichment. [1]
External storage workaround: Write the full JSON to Google Sheets with an ID reference, then import summarized data back into Clay using lookup actions.
Split strategically: Use formulas to split content across multiple cells - one for the first 4,000 characters, another for the remainder.
Since you mentioned JSON formatting issues, could you copy and paste the specific JSON structure you're working with? This will help me suggest the best field paths to extract your needed data efficiently.
If you still need help with managing the JSON size limit or have more details to share about your integration challenges, I’m here to assist. Would you like to provide more information about what you’re trying to achieve or any specific issues you’re encountering?
whats the usecase? what you are trying to do?
can you enrich contacts directly in your app instead of clay?
Based on your earlier message about JSON size limits, it sounds like you're trying to export complete enriched contact data from Clay to use in your own application.
For direct enrichment in your app instead of Clay, you have a couple options:
What specific enrichment data are you looking to get, and what's your target destination system?
If you still need assistance with your JSON enrichment or integration setup, I’m here to help. Would you like to share more details about your use case or any specific challenges you’re facing?
Thank you for your message. If you have any questions or need further assistance, feel free to share more details about your use case or challenges.
share publically as a christmas gift Willy H.
Clay has two cell size limits: 8KB for basic columns and 200KB for action columns. [1] Here are effective workarounds for large JSON exports:
Split data strategically: Use formulas to split content across multiple cells - one for the first 4,000 characters, another for the remainder.
Use field paths for precision: Instead of exporting full JSON, use dot notation like Results.child.grandchild to fetch only specific subsets of data you need.
External storage approach: Write the complete JSON to Google Sheets with an ID reference, then import summarized data back into Clay using lookup actions.
Process externally: Use third-party tools like Postman to execute API queries externally before importing the processed data into Clay.
Since you mentioned JSON formatting issues, could you copy and paste the specific JSON structure you're working with so I can suggest the most effective field paths for your needs?
If you still need help with handling the JSON size limit or have more questions about your integration, I’m here to assist. Would you like to provide more details about your use case or any specific issues you’re encountering?
