Google Drive Not Appearing

I am trying to integrate my Google Drive for a google drive trigger . I went through all the steps for my OAuth a number of times. Connection is successful. However, the drive (and subsequent folders) doesnt appear on the dropdown list. It’s listing mostly local files and a bunch of jibberish. Any suggestions?

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

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

Are you choosing the right option from the “Trigger on” dropdown?
there are two options:
1- Changes to a Specific File

2- Changes Involving a Specific Folder

if you are seeing only the files, then you must have selected option 1, which will only get you the files in the field “File”, see below attached picture for better understanding.

Hey Lokesh - thanks for the reply.
It’s not a matter of Folder or File. Either way, it’s not looking into my google drive. It’s populating local drives.
Very weird

That’s really strange @Bob_Cal . So, it’s like the node is defaulting to local drives instead of your Google Drive connection. That might suggest an issue with how the node is configured to use the Google Drive connection.

Can you try re authenticating the Google Drive connection or re selecting it in the node settings? Sometimes, re starting the connection can resolve issues like this.

Also, are you using the correct node for Google Drive?

If you’re still having trouble, feel free to share a screenshot of your node settings, and I can take a closer look.

Good luck bud

Thanks for the reply Zelite.
I tried it again in a new workflow.
Same settings:
Google Drive Trigger>
On Changes to a specific folder.

Made a new project in google console. Went through all the steps again. Added a test user. Connection was successful. Yet still, the dropdown list only shows local info.

Driving me nuts. ha

@Bob_Cal can you change the drop down menu from “From list” to “by url” a new field “Folder url” should appear. Then paste your google drive folder url.

This should work

That’s what inside your Google Drive tho, you can search for a folder with keywords.

Google Drive n8n node is rendering A-Z in ascending orders.

They, Cutecatcode – I thought that too at first, but my google folders arent there.

Is your folder in shared drives?

Hey.. thanks again.
I did try that previously with no success.
I tried it again just now as well.
I tried a slightly different flow - chat to create folder. Pointed it to the url of the test folder.
It said everything executed correctly, but when I search my google drive and my local drive, no folder created.

For this one, it could very well be the I am not using the node correctly. But wanted to give it a try.

The bottom line still, when “My Drive” is selected as parent drive, the parent folder structure doesnt represent what’s in MyDrive.

(thanks for your help and attention)

I think you might be on to something here. Literally when through this as you were sending your message. Checking now

Nothing I can do there. Its a personal gmail account. I cant make a new shared drive.
Still weird. I double checked the From List, with the Parent Folder as MY Drive. I am getting some, but not all the folders in the drive.

And the weirdness continues, with a possible solve.
I noticed that the folders that do populate under the folder list where the ones that I had named with an * in front of them. There are about 50 folders. Ten or so with the *…. those ten DO show up in my dropdown.

So I created a new folder for this test, with an ** — and viola, it’s in my dropdown.

noticed here the AI input doesnt name the folder. I do see that field in node settings.
Everything is working now with the * trick.

Thanks to everyone for the help. Though this is still buggy, I do have the work around and can continue my learning journey here!

You are welcome buddy @Bob_Cal and I am happy I was able to able to help.

Kindly mark as the solution to help others