Google Drive upload node fails on second loop iteration

Questions
,
1

Hi everyone :waving_hand:

I’m facing a strange issue in one of my workflows and would really appreciate your help.

Context

I have a workflow that:

  • Downloads files from Dropbox

  • Uploads them to Google Drive

  • Runs inside a loop (multiple files)

The workflow is quite complex but has already worked multiple times in the past, so I’m confident the global logic is correct.

Issue

Screenshot 2026-03-24 at 5.59.56 PM
Screenshot 2026-03-24 at 5.59.56 PM2940×1912 451 KB

  • :white_check_mark: 1st iteration: everything works perfectly (download + upload OK)

  • :cross_mark: 2nd iteration: the Google Drive upload node fails every time

What’s weird is:

  • The input of the node looks correct

  • This issue appeared suddenly (it was working before)

  • Restarting or reloading the workflow doesn’t fix it

What I’m sharing

  • :movie_camera: A video of the workflow execution

  • :camera_with_flash: A screenshot of the input data for the failing node

Question

Has anyone experienced something similar with loops or Google Drive uploads?

Could it be:

  • A binary data issue?

  • Something getting lost/mutated between iterations?

  • A limitation or bug in the Google Drive node?

Any ideas or things I should check would be super helpful :folded_hands:

Thanks a lot!

1 Like
2

yeah this looks like binary data mutation between loop iterations — metadata from the first upload sometimes carries over. quick test: throw a debug node right before the google drive upload to see what iteration 2 actually receives, if the data looks different thats your culprit

3

hi @Tal_Benhamou , welcome to the n8n community!

One thing I’d check is whether you actually need the loop there. The Google Drive node can usually process multiple items directly, so an extra loop may be re-feeding mutated items on the second pass. I’d also verify that no Set/Edit Fields node before upload is dropping the binary data (Include Binary Data).