Cell Data Size Limit Exceeded in Google Maps API Results

Joe H. · 2025-11-14T05:20:34.930Z

Getting an "Cell data size exceeds limit (200 kB)" result on a meaningful portion of HTTP API results. The API scrapes Google Maps

Cell Data Size Limit Exceeded in Google Maps API Results | Clay

7 comments

· Sorted by Oldest

Clay Support
APP
·
·
The 200kb cell size limit is a fixed constraint in Clay. To resolve this, you can:
Split the data: Use API parameters like limit and offset to break large datasets into smaller chunks.
Target specific data: Use dot notation to fetch only specific subsets (e.g., Results.child.grandchild) instead of pulling complete datasets.
External processing: Write large data to Google Sheets with an ID reference, then import summarized data back into Clay using lookup actions.
Since you're getting this error with Google Maps API results, consider requesting data incrementally (location by location) rather than bulk requests.
Could you copy and paste your JSON request body so I can help troubleshoot the specific structure causing the size issue?
Joe H.
·
·
Loading attachments
Joe H.
·
·
Loading attachments
Clay Support
APP
·
·
Your current setup with limit=75 is good for managing the 200kb cell limit. To further optimize:
Reduce the limit parameter - Try setting it to 25-50 instead of 75 to get smaller result sets.
Use dot notation to target specific data subsets instead of pulling complete datasets (e.g., Results.places.name instead of the full response).
Process incrementally - Consider running smaller batches of coordinates rather than processing many rows simultaneously.
Could you copy and paste your JSON request body so I can help troubleshoot the specific structure causing the size issue?
Joe H.
·
·
There is no JSON request body - the query param is "query" in the screenshot
Clay Support
APP
·
·
You're correct - since you're using GET with query parameters, there's no JSON body. For your Google Maps API hitting the 200kb limit with limit=75, try reducing the limit to 25-50 results per request.
You can also use dot notation to target specific data subsets instead of pulling complete datasets (e.g., Results.places.name instead of the full response).
Could you copy and paste the actual API response or error details you're seeing in the cell? This will help identify which specific data fields are causing the size issue.
Clay Support
APP
·
·
If you still need help resolving the "Cell data size exceeds limit" issue, I’m here to assist. Would you like to share more details about the API response or error so we can troubleshoot further?

Clay Support
APP
·
·
The 200kb cell size limit is a fixed constraint in Clay. To resolve this, you can:
Split the data: Use API parameters like limit and offset to break large datasets into smaller chunks.
Target specific data: Use dot notation to fetch only specific subsets (e.g., Results.child.grandchild) instead of pulling complete datasets.
External processing: Write large data to Google Sheets with an ID reference, then import summarized data back into Clay using lookup actions.
Since you're getting this error with Google Maps API results, consider requesting data incrementally (location by location) rather than bulk requests.
Could you copy and paste your JSON request body so I can help troubleshoot the specific structure causing the size issue?
Joe H.
·
·
Loading attachments
Joe H.
·
·
Loading attachments
Clay Support
APP
·
·
Your current setup with limit=75 is good for managing the 200kb cell limit. To further optimize:
Reduce the limit parameter - Try setting it to 25-50 instead of 75 to get smaller result sets.
Use dot notation to target specific data subsets instead of pulling complete datasets (e.g., Results.places.name instead of the full response).
Process incrementally - Consider running smaller batches of coordinates rather than processing many rows simultaneously.
Could you copy and paste your JSON request body so I can help troubleshoot the specific structure causing the size issue?
Joe H.
·
·
There is no JSON request body - the query param is "query" in the screenshot
Clay Support
APP
·
·
You're correct - since you're using GET with query parameters, there's no JSON body. For your Google Maps API hitting the 200kb limit with limit=75, try reducing the limit to 25-50 results per request.
You can also use dot notation to target specific data subsets instead of pulling complete datasets (e.g., Results.places.name instead of the full response).
Could you copy and paste the actual API response or error details you're seeing in the cell? This will help identify which specific data fields are causing the size issue.
Clay Support
APP
·
·
If you still need help resolving the "Cell data size exceeds limit" issue, I’m here to assist. Would you like to share more details about the API response or error so we can troubleshoot further?