I am trying to send 2k rows with 8 columns into a Google Sheet, and it is taking some time to land in the spreadsheet. Only 400 rows have been pushed in 2 hours, is this normal?
Pushing 400 rows out of 2,000 in 2 hours is slower than expected. The Google Sheets integration creates a live connection where data should appear in real-time as rows are processed. [1]
To troubleshoot:
Check if all rows in Clay have finished processing their enrichments before being sent to Google Sheets
Verify the integration is running on all rows (not just a subset)
Review any error messages by clicking into cells where the Google Sheets action ran [2]
If the issue persists after checking these items, ask to speak with a human for further investigation.
Did that help resolve your issue?
no errors, the integration seems to be working fine
Thanks for letting me know. I’ll connect you to a human agent who can assist you further with this issue.
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

Hello Tommy! Thanks for reaching out! Clay is definitely slower than usual today. Let me know if this persists even after an hour. Will flag this to the team regardless. Have received quite a few reports on this.
Hey Sayli, thanks for the quick response. The integration only pushed 1868 rows instead of 1935. What's the best way to backfill?
Hey
To backfill the missing rows, you can rerun only the ones that errored out:
Right-click on the Export to Google Sheets column header.
Add a filter and set it to “Has error”.
This will show you just the rows that failed.
Select those rows and rerun the export for them.
That way you only retry the ones that didn’t make it into the sheet.
Let me know if you have more questions.
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!
