also seeing that Google Sheets integration just stopped working (can’t read the column titles anymore). Tried new table, new sheet, login, reset etc.
Google Sheets integrations can fail due to rate limits - there's a default limit of 300 read requests per minute per project. When this limit is exceeded, Google temporarily blocks requests until the quota resets (typically after a minute). Also check if you're using the correct Google account for the integration. If you're using the wrong account, remove the connection and reconnect with the correct Google account. Try waiting a minute and retrying the request, as the quota resets every minute.
ok my mistake. Accidentally created a dupliacte header in sheets. UI is weird on this tho
Hey Andreas! Happy to help✨. Sorry about this. We’ll share this with the product team to improve the error messaging. Let us know if you still run into any issues.
Hey Daniela, great - I now have internalized how brittle this is with regards to column titles sheets-side. For new users this will be much better with clearer signs what’s wrong yes! Also, this happened in between: https://www.loom.com/share/82234a5f045c4479b828da53a5380fa5?sid=a7e89451-e9b4-4c8f-b245-601b6c846607
Hey Andreas! Happy to help✨. That is very odd. Are you still experiencing this issue? I just ran some tests in your table and couldn't replicate this.
it happens when tyhe column titles in the G sheet are not unique.
which is logical but it’s not communicated correctly
Totally hear you. Got it. We'll share this with the engineering team. Thanks for flagging!
How about google sheet as a source! Seems like a no brainer! Andreas just watched some of your vids on the topic
Hey Devin! Thanks for the further suggestion! I know this may sound like a silly question, but can you give me further context on why Google sheet as a source would be helpful for your use case? Once I have that as feedback I can pass it on to the product team as "Here's an idea that seems like a no brainer AND here's why specific customers think it will improve their workflow!" I look forward to your response! :)
Here’s a good example: I ran a google review scrape at a company level using apify that dumps into a google sheet. I did this because every time I try to pull the results in from apify directly the output gets truncated to 20 reviews only when i need to run analysis on a bigger sample set, and it also only pulls in the most recent apify pull instead of appending the table with new content. So the google sheet has a ton of great data in it. Right now I have to have it wired up through a webhook to dump into clay. it seems super unnecessary when a google sheet could just be the source. Let me ask what the reasoning is for not allowing a google sheet as a source?
Hey — totally get why this feels frustrating, especially since you’ve already got a clean dataset in your Google Sheet. The reason Google Sheets isn’t supported as a direct source right now comes down to a few technical constraints: 1. Row order issues Clay processes large datasets in parallel chunks (e.g. rows 200–300 might load before rows 0–100). Google Sheets doesn’t guarantee order when syncing this way, which caused confusion. Supporting Sheets would require changing Clay to process data synchronously, which goes against how sources are currently built. 2. Google’s API rate limits Google’s API is slow and rate-limited. Clay would need to batch requests in larger chunks to make it efficient, which just worsens the row order problem. 3. Infrastructure constraints Fixing both of these would mean a significant overhaul to how Clay handles sources. Because of that, Google Sheets as a source was disabled and marked as a lower priority for now. Current recommendation: • Keep using your webhook setup (which is working well in your case) • Or upload your data as a CSV • Tools like Zapier can also help sync Sheets → Clay if you’re looking for an alternative
Sorry for this Andreas!!