n8n - 💡(How to fix) Fix Google drive node does not download documents [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28633Fetched 2026-04-18 05:56:59
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

When trying to download a newly created document using the Google Drive node, the node runs successfully but the document is not downloaded

<img width="821" height="576" alt="Image" src="https://github.com/user-attachments/assets/216427e1-0b77-4623-84df-b5cac30ebfce" />

This behavior is random, as some runs download the document normally and others do not.

To Reproduce

  1. Workflow creates a copy of a document
  2. Dynamic fields are inserted into this copy of the document
  3. The Google Drive node should download this updated document
  4. The node runs successfully, but does not download the document. It also doesn't go down the failure path.
<img width="1633" height="641" alt="Image" src="https://github.com/user-attachments/assets/ff31f39e-6084-441e-98b3-1094daf70b6e" />

Expected behavior

The expectation was that this node would download the document that was created a few nodes ago. This binary is later converted to Base64 and sent to Salesforce.

<img width="1486" height="652" alt="Image" src="https://github.com/user-attachments/assets/2a3c7d29-162c-4538-8a7d-2b39687bcc89" />

Debug Info

Debug info

core

  • n8nVersion: 2.13.3
  • platform: docker (cloud)
  • nodeJsVersion: 24.13.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 20
  • license: enterprise (sandbox)
  • consumerId: 00000000-0000-0000-0000-000000000000

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36 edg/147.0.0.0
  • isTouchDevice: false

Generated at: 2026-04-17T18:00:45.866Z

Operating System

Windows 11 Pro

n8n Version

2.13.3

Node.js Version

?

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

extent analysis

TL;DR

The Google Drive node may not be downloading the document due to issues with the node's configuration or the document's availability, and verifying the node's settings and the document's permissions could help resolve the issue.

Guidance

  • Check the Google Drive node's configuration to ensure it is set up to download the correct document and that the document is shared with the correct permissions.
  • Verify that the document is being created successfully and is available in Google Drive before attempting to download it.
  • Review the workflow's execution history to see if there are any patterns or errors that could be contributing to the issue.
  • Consider adding error handling to the workflow to catch and log any errors that may be occurring when the Google Drive node runs.

Example

No code example is provided as the issue does not include specific code details.

Notes

The issue's randomness and lack of error messages make it difficult to pinpoint the exact cause, and further debugging may be necessary to fully resolve the issue.

Recommendation

Apply workaround: Add error handling and logging to the workflow to catch and log any errors that may be occurring when the Google Drive node runs, and verify the node's configuration and the document's permissions to ensure they are correct.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The expectation was that this node would download the document that was created a few nodes ago. This binary is later converted to Base64 and sent to Salesforce.

<img width="1486" height="652" alt="Image" src="https://github.com/user-attachments/assets/2a3c7d29-162c-4538-8a7d-2b39687bcc89" />

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Google drive node does not download documents [1 comments, 2 participants]