New feature's Send table data (now that write to another table is deprecated) just ruined my whole file. I had 2600 rows, it just disapeared when i updated some new rows. how do i do
I understand how frustrating this must be. Unfortunately, Clay doesn't track row history or deletions, so there's no way to recover the previous data directly.
You can try using Cmd/Ctrl + Z to undo recent actions like row deletions, but this only works immediately after the action and won't recover enrichment runs. [1]
For the missing 2600 rows, you'll need to re-import or manually update the data. Before doing anything else, I'd recommend trying our built-in AI tool Sculptor (top-right corner) - it can help you rebuild tables and set up workflows quickly. Give it a try and let me know if that helps recover your setup.
Is that what you were looking for?
why did u freaking delete this write to another table, now we can't update any file anymore without loosing everything
I'm sorry to hear about the frustration this has caused. 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!

Hey Félix, I'm really sorry about this. This is the first time I've seen this behavior. Would you mind explaining the steps you took before the data disappeared?
i just sent data to table, then mapped my data in the corresponding columns, then every legacy column got erased
Hello Félix! Thanks for reaching out! Jumping in for Mitch here. Can you send me the table link URL? I want to take a closer look into what happened. There is a possibility this data got overwritten.
Yes it is, tbh i already modified it ! no worries. But : why did the "write to another table" got disabled ?
I am not completely sure but I believe the interface was a little confusing so we have considered a lot of product feedback to create a better functionality for the customers. I am sure there might be some engineering considerations as well.
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!
