Fixing Clay and Google Sheets Integration Issues: Data Overwrite Problem

Arne S. · 2024-12-06 09:32:41.116129+00

Hi, I am having a problem with the Clay <> google sheets integration. I am using the ‘Lookup, Add, and Update’ function in Clay. The records are added in google sheets, but overwrite the data in the second row. Weirdly though, it has written about 90 rows properly. How could I fix this?

Fixing Clay and Google Sheets Integration Issues: Data Overwrite Problem | Clay

Channeled
APP
·
·
To resolve this issue, please check your configuration in the "Lookup, Add, or Update Row" action settings: 1. Verify your Lookup Column and Lookup Value settings are correctly specified. These are crucial for determining which rows to update. 2. Review your Row Behavior settings: • Ensure "Add a row if no existing rows are found" is enabled if you want to add new rows • Check if "Update row(s) if existing rows are found" is configured correctly for your needsIf the issue persists after verifying these settings, you may want to request human support as this could indicate an unexpected behavior that needs further investigation. Source: Google Sheets - Clay University
Channeled
APP
·
·
Hi Arne S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Arne S.
·
·
I checked the things above, it still doesn’t work properly. I can see the google sheets second row get overwritten real time
Tanvi R.
·
·
Hi Arne, thanks for reaching out! Just to clarify, was data from the second row already in the Google Sheet or was this information sent over from Clay?
Arne S.
·
·
The data in the second row was already in the google sheet, but sent over from Clay earlier. So both I guess?
Tanvi R.
·
·
Got it Arne, thanks for clarifying!
👍1
Tanvi R.
·
·
Hey Arne, could you make this Google Sheet public? I noticed the google sheet is not set to public. If it is private Clay will not be able to access it. Let me know if it does the trick!
Channeled
APP
·
·
Hi Arne S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Arne S.
·
·
Tanvi R. Well, I do not want to make the google sheets public, this is important information for our business. The Clay account is connected to our google drive, and it has shown to be able to send information to the particular google sheet. The problem is that it keeps overwriting the second row (the first row is a header row) when information is sent.
Bo (.
·
·
Hey! That's definitely frustrating when Sheets starts overwriting data! The quickest fix is usually to start with a fresh Google Sheet. But to help figure out exactly what's happening - could you let me know which specific rows in Clay got overwritten? I can check the backend and pinpoint why it's happening with those particular rows. This is usually related to how the data is formatted, and once we know which rows are causing trouble, we can solve it! 🙂
Arne S.
·
·
Yeah it’s pretty annoying, but hey, look at it from the bright side, I really want to use it! 😉 I started with a fresh sheet, it seems to work properly now. Any tips on preventing such a thing from happening again? So before all rows would actually overwrite.
Daniel K.
·
·
Hey there, thanks for reaching out! ☺️ Perfect and sorry for the hiccup! Next time this happens, can you share the link to the table so we can investigate right away? Right now it's going to be difficult to replicate this without knowing what happened on the backend server. Btw, we'll be reworking the Gsheet integration soon to make sure these hiccups don't happen again. Generally, I'd recommend other database solutions to Gsheet as the rate limits can be frustrating as well. Have you considered using no-code databases? Here are a few options that I would recommend: - NocoDB - Seatable.io - Baserow.io - Gigasheet - Airtable - Xano (more technical) - Supabase (more technical) If there's anything else I can assist you with, please let me know! 😊 Have a great Friday, Daniel

17 comments