What is your goal?
i want google drive to detect my folder.
What is the problem & what have you tried?
the google drive module ( Staff Name ) can’t detect folders despite having all the field in the module correctly, i have tried all there is to try in make.com, the problem started when i switched to a shared drive, it didn’t existe when i was on ’ my drive ’
Error messages or input/output bundles
there is no error messages, instead of showing ’ Total number of bundles equals 1 ’ it shows ’ 0’ which means it didn’t find any folder with the query
Create public scenario page
Screenshots (scenario flow, module settings, errors)
Hello,
Welcome back!
That’s expected – Google Drive API treats My Drive and Shared Drive as two completely different entities, and the API calls need to reflect that.
When you query a regular folder (My Drive), a basic parameters works fine.
But for Shared Drive folders, API requires a few additional parameters so folder/file ID for file existing in “Shared Drive” is not enough to fetch it correctly.
Without those, the API silently returns an empty result – no error, no warning. So if your scenario worked on My Drive and now returns nothing, that’s most likely the reason.
If your scenario needs to handle both types (files from My Drive and Shared Drive), you’ll need to split the logic – for example with a Router – and apply the correct parameters depending on the source.
Have a nice day,
Michal
Hello, thank you for the explanation but how do i fix the problem really? I can t find In the module parameters fields that can fix the problem. I only want it to detect on shared drive
Hello,
When setting up the module, change Drive from My Drive to Google Shared Drive.
Your scenario share link was disabled by you, so I cannot point out which exact module you have used in your scenario.
Have a nice day!
Michal
Had the exact same issue — the folder existed but Make just wouldn’t pull it up in the dropdown. Turned out the Google account connected to the module didn’t have direct ownership of that folder, it was shared from another account. Re-connecting with the right Google account fixed it immediately. Also worth trying: use the folder ID directly instead of browsing for it, that bypasses the detection issue entirely.