Google Drive Node - Unable to Browse Folder Hierarchy - n8n v1.73.1 (Cloud & Local)

[lucasjameso]

Bug Description

The Google Drive node is unable to browse or list the complete folder hierarchy, despite successful authentication and broad permissions. This issue occurs on both my n8n.cloud instance and my local n8n instance (version 1.73.

To Reproduce

{
"nodes": [
{
"parameters": {
"resource": "file",
"operation": "list",
"returnAll": true,
"options": {}
},
"name": "Google Drive",
"type": "n8n-nodes-base.googleDrive",
"typeVersion": 1,
"position": [
450,
300
],
"credentials": {
"googleDriveOAuth2": {
"id": "123", // This would be the credential ID in your n8n instance
"name": "Google Drive Test"
}
}
}
],
"connections": {}
}

Expected behavior

The Google Drive node should allow browsing and selection of all folders within the connected Google Drive account.

Observed Behavior:

Only a limited set of files and folders are visible at the root level of the Drive.
Navigation into subfolders is not possible.
The dropdown or folder selection mechanism does not function correctly.

Environment:

n8n.cloud: (Production)
Local Instance: n8n v1.73.1
Node: Google Drive
Operating System (Local): Windows, Linux
Deployment Method Cloud & n8n locally -Docker
Permissions Granted:

n8n has the following Google Drive permissions:

../auth/drive (See, edit, create, and delete all of your Google Drive files)
../auth/drive.photos.readonly (View the photos, videos, and albums in your Google Photos)
../auth/drive.appdata (See, create, and delete its own configuration data in your Google Drive)
Troubleshooting Steps Taken:

Verified connection to the correct Google account.
Created new Google Drive credentials and re-authenticated.
Tested with a simplified node configuration:
Resource: File
Operation: List or Get Many
Return All: True
Folder ID/Parent Folder ID: root (and also tried leaving it blank)
Confirmed no filters are applied in the node or in Google Drive.
Checked that no folders are hidden in Google Drive.
Confirmed the "Source" option is set to "My Drive".
Replicated the issue on both n8n.cloud and a local n8n instance (v1.73.1).
Verified the issue is not present when using the "Shared with me" source option, indicating the problem is specific to "My Drive" folder listing.

Request:

Please investigate this issue, which appears to be related to how n8n interacts with the Google Drive API for folder listing.

Are there any known issues with Google Drive folder browsing in n8n v1.73.1 or n8n.cloud?
Could my n8n.cloud instance be restarted to rule out instance-specific problems?
Are there any relevant error logs or debugging information I can provide from my end (especially from the local instance)?

Operating System

Windowss Local and Cloud version

n8n Version

1.73.1

Node.js Version

Google Drive node version 3 (Latest)

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @lucasjameso,

We have created an internal ticket to look into this which we will be tracking as "N8N-8000"