Gmail CSV Attatchment Download Truncated from 3kb to 300b

[Adam_Durey]

Describe the problem/error/question

Gmail Trigger Downloads PDF and CSV attachments from email and parses them for detail - but the csv is mojibaked (garbled).

I tried several encodings and no luck.

To check further, I download the csv file to my local drive from the gmail node output but it is definitely baked.

So I downloaded the csv directly through Gmail and it is fine.

What is the error message (if any)?

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

• n8n version: 1.86.0
• Database (default: SQLite): default
• n8n EXECUTIONS_PROCESS setting (default: own, main): default
• Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
• Operating system: Windows

[danougill]

Hey there, it’s working totally fine for me in CSV. Could you check to make sure that your csv file locally isn’t corrupted? I will say, pdf definitely looks a garbled. Could it be that you’re passing in a pdf instead of a CSV?

[Adam_Durey]

Thankyou for reaching out to help.

For clarity - I was a few updates behind when this problem occured - I moved up to the latest version in effort to trouble shoot - so I dont think this is a new issue in n8n - it may be unique to me.

I resent the email without the PDF to be certain there was no conflict.

Now admittedly the garbeling looks different but its still garbled.

Regardless - If I view/download the csv directly from the Gmail Node the file is clearly corrupted

[Adam_Durey]

I configured a Imap Trigger node to test but the .csv is still coming through corrupted.

---

I can see that the file size is being truncated from 3kb to 300bytes

---

My Script still handles the downloaded pdf’s fine.

---

I was forwarding the email to myself to test the IMAP Trigger and test different email formats.

The process works when I go back to the source email, the error has something to the email being forwarded from the same inbox, or from be sufficiently far down in the conversation/email-chain.

[danougill]

Hey there, could you check if your csv works if you open a text editor? Thanks

[Adam_Durey]

Thanks Danougill - You can see about the csv opened in a text editor - you can also see that the Gmail node truncated the csv filesize by 90%.

I am working around this fine now anyway, just something to be aware of moving forward.