Issue with unzipping a ZIP file in an n8n workflow

Describe the problem/error/question

I am facing an issue with unzipping a ZIP file in an n8n workflow. I use an IMAP Trigger node to fetch my emails and successfully retrieve a ZIP file in binary format. However, when I use a node to unzip this file, I cannot get the unzipped file as an output of this node.

What is the error message (if any)?

No specific error message.

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 0.224.4
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud and docker
  • Operating system: Linux , MacOS

Hi @momo2001tn, welcome to the community!

I just tried running your workflow, but wasn’t able to reproduce the problem. On the IMAP Trigger not itself I could see the ZIP file:

On the compression node I can see the two files from my ZIP file:

Could you perhaps share the output you are seeing on your Compression node, so I can get an idea of the problem?

This is what I got out. I have no file, I am waiting for a csv file

Now that is interesting indeed. I wonder if n8n struggles specifically with your ZIP file. Are you also seeing this problem when reading the very same ZIP file through any node other than the IMAP node and then trying to decompress it?

Could you perhaps create a test ZIP file using which this problem can be reproduced (without anything confidential in it of course) and share it?

when I download the ZIP file using an HTTP request, I don’t have any issues. However, I can send the file, but as soon as I remove the information, it can successfully perform the decompression. Therefore, it would be better for me to send it to you privately.

Thanks @momo2001tn, I got the example via DM and was able to reproduce this problem on my end.

I suspect it has to do with the uppercase file ending .ZIP instead of .zip. Can you try converting the file extension to lowercase and confirm if this works for you?

For example like so:

This should update the respective field:

New version [email protected] got released which includes the GitHub PR 6098.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.