How can I work around Clay's 8KB cell size limit when exporting complete JSON enrichment data?

You have several options to handle large JSON exports: 1) Use field paths with dot notation (like data.contact.email) to extract only specific needed fields instead of the full JSON, 2) Use bulk enrichment to process datasets and export results directly to external destinations like Salesforce, Snowflake, or Google Sheets without storing in Clay, 3) Write the full JSON to Google Sheets with an ID reference, then import summarized data back into Clay using lookup actions, or 4) Consider enriching contacts directly in your own application using Clay's data enrichment tools with your existing API subscriptions.

You have several options to handle large JSON exports: 1)

// Legacy reference

This page is kept as a narrow support reference from the older GTM Stack corpus. It can still be useful for one-off operator questions, but it is not one of the curated flagship entries. Start from the curated question set if you want stronger workflow guidance.

02Community answers1 response

You have several options to handle large JSON exports:

Use field paths with dot notation (like data.contact.email) to extract only specific needed fields instead of the full JSON,
Use bulk enrichment to process datasets and export results directly to external destinations like Salesforce, Snowflake, or Google Sheets without storing in Clay,
Write the full JSON to Google Sheets with an ID reference, then import summarized data back into Clay using lookup actions, or
Consider enriching contacts directly in your own application using Clay's data enrichment tools with your existing API subscriptions.

GTM StackLegacy reference