For CSV import field issues, try these troubleshooting steps:
Field Mapping Problems:
Ensure your CSV uses UTF-8 encoding with comma separators
Remove commas, colons, and semicolons from your CSV data as these can cause field mix-ups
Try uploading to Google Sheets first, then download as CSV and re-import
Column Processing Issues:
If specific columns aren't updating correctly:
Delete the affected column
Create a fresh column
Re-map your data to ensure proper field matching
CSV Import Limits:
Verify your file has maximum 72 columns and 50,000 rows, with a short filename
For the "page not found" error when deleting zero-data imports, this appears to be a technical issue. If you need further help with this specific deletion problem, please request human assistance by clicking on "Talk to a person." [1]
Was that helpful?
No. I've already tried those tips...
I'm sorry those tips didn't help. I'll connect you to a human agent who can assist you further.
Hi Fernanda - thanks so much for reaching out. Could you please share the table link in which you're having the issue? To clarify - the problem is that when you are importing a CSV the columns are not getting mapped correctly?
Hey Aditi S., thanks! Here is the table link. The issue is that besides the columns being mapped correctly, they are not updated with the respective data. And there is actually fields I can even delete from the overview that now seems messed up...
It's a little tricky here to figure out which CSVs you're having issues with specifically within this workbook, because there are quite a few different ones you have within this. I can also see that multiple CSVs are being imported into the same table, and I am not 100% sure how you've mapped each one, which may also be causing issues. Is it possible to start a fresh workbook and just import one of the CSVs you're working with then troubleshoot specifically the mapping of that?
Actually, the CSVs you're seen have imported zero data from the fields I needed. All CSV records are the same, they have been mapped the same way (I only needed email addresses Clay providers couldn't find), the number of CSVs just account for how many times I mapped the fields and tried to import...
Nothing happened
What I'm trying to say with it all is that I can do it manualy but it is not sustainable at scale.
Thanks for the context Fernanda - I have a few questions, which will help me with troubleshooting better here.
I see that it is the same file being uploaded multiple times. Could you help me understand what the goal here is with importing the CSVs and how you are wanting this workflow to work? To clarify, within Clay, you will have to manually upload CSVs, as we don't have an automatic way to do this.
I see now that the issue with the CSV import is that the data from the CSV is not getting inputted into your table. I am curious as to why this is happening specifically and it would be really helpful if you could create a separate table / workbook to just individually import the CSV so we can try to see what is going wrong with that action.
I only need to update emails from the CSV Email column to Apollo Email Search column created manually on Clay as I mentioned here. I know it is a manual process but I need it to work as copy+paste isn't scalable (saying it because it is not the first time I have to update data with a CSV, and even mapping fields correctly and it doesn't work).
Hello Fernanda! Thanks for reaching out! Can you send me one of the CSVs? I would like to try and see why this column is not getting added correctly.
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!
