GDrive "removes" binary file from workflow

[MP_TL]

Describe the problem/error/question

In my workflow, I use binary file fetched from Gmail and upload it to GDrive. Everything works well until I put in a GDrive node before the upload. After that node, the binary file is not available in outputs from previous steps, as if the node was “clearing” the binary files. Am I doing something wrong?

I tried moving the GDrive node around, and every time I put into the flow, right after it, the binary files disappear.

Thanks!

Please share your workflow

Share the output returned by the last node

This operation expects the node’s input data to contain a binary file ‘data’, but none was found [item 0]

Make sure that the previous node outputs a binary file

Information on your n8n setup

• n8n version: 1.51.2
• Running n8n via cloud
• Operating system: Mac OS

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

[ria]

Hi @MP_TL

Thanks for posting here and welcome to the community!

You can use a merge node to retrieve the binary from previous nodes.
Here is an example:

Send PDF from email to Google Drive with several steps

Hi @saachi welcome back to the n8n community! The parameter “Input Data Field Name” is expecting the name of the input binary field that contains the attachment, so the binary file must be there in the previous node. A way to do that is by using a Merge node to add the binary files coming from the initial Gmail node into the input of the latest Google Drive node. In this way the binary files will be available. See demo workflow: I hope this helps

Hope it helps!

[MP_TL]

OMG, you’re such a legend @ria . Thank you so much!