Re-using a binary file at the end of a workflow

Describe the problem/error/question

Hello n8n community!

I’m currently working on a workflow that receives an image through a form submission. If the uploaded file is a PDF, I convert it to an image so it can be sent via an HTTP request.

The binary file is then sent to an AI agent to extract data, and I’m successfully processing that data within the workflow — so no issues there.

However, I’m running into trouble at the end of the workflow, where I want to upload the original (or transformed) binary file to my cloud drive. This part isn’t working as expected, and I’m not sure how to properly handle the binary upload.

Does anyone have advice or best practices for uploading binaries to a drive at the end of a workflow?

Thanks a lot in advance!

What is the error message (if any)?

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

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.88.0 (Self Hosted)
  • Database (default: SQLite): Default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Debian

You need to change the Merge’s node mode to Combine by position.

If this resolves your issue, please mark this post as a :white_check_mark: Solution.

1 Like

It works ! thank you.

I tried to solve this for 2 days and the solution was so simple :sweat_smile:

Glad it worked.

In Append mode the Merge node produces a sequence of items.

Happy n8ning!

1 Like

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