Hi, I’ve tested the google drive service account plugin extensively and it seems like it’s not able to access shared drives.
I shared a regular folder with it from my organization, and it worked perfectly.
When I shared a folder from a shared drive, it can’t access it.
I believe all that’s needed is to add the query parameter supportsAllDrives=true to the API calls for this to work. I’m blocked on an important project for a vital client, and hoping this can be resolved quickly.
Hi @gio,
Thank you for your message and sorry for the delayed reply over the weekend.
When you have a moment, could you please provide more screenshots showing how your app is set up, the details of the plugin element you’re using, the related workflows, and the specific error message that appears?
If possible, please record the process in Step-by-Step mode using tools such as Loom, and share a link with us.
This info will help me verify with the dev team and get back to you with additional information.
Thank you and looking forward to your reply.
Regards,
However, it didn’t apply to some of the other actions. For example, I am now able to access a shared drive folder with the “Get file” action, but I’m not able to search for files in a shared drive.
(Please forgive the weird audio, my loom recorded my music instead of my voice)
I’m able to get the folder to show up, but when I search for its children none show up despite it being a valid query.
In order to support drive searches, the files.list action must have these parameters:
supportsAllDrives: Set this to true to include shared and team drives in the response.
includeItemsFromAllDrives: Set this to true to consider files and folders in all drives, not just those in the user’s “My Drive”.
driveId: (Optional) Specify the ID of the shared or team drive to search within that specific drive.
corpora: (Optional) Set to drive to search a specific drive when you’ve specified the driveId, or allDrives to search all available drives.
You could choose to support filtering by a specific drive which would be great, but even just adding the following parameters should fix it:
Thanks Igor! Quick note: I’m hoping shared drive support will be available for all the actions rather than just the ones I’m mentioning—for example I’m hoping to be able to create a folder in a shared drive.
I’m excited to share that we have effectively resolved the issue with the Complete Google Drive (Service Acc.) Plugin action and have updated it to version 1.22.0
Could you kindly update the plugin within your app to this latest version and confirm whether everything is now operating smoothly?
Feel free to explore the plugin’s functionality on our demo page.
Your patience and cooperation throughout this process have been greatly appreciated.
Would like to notify you that we’ve updated the Complete Google Drive (Service Acc.) Plugin to Version 1.23 and Added parameter “q” for API call "Get Files (API v3) Extended"
When you get a chance, please update the plugin inside your app to the latest version and let us know if it is functioning now as expected.
Thanks again, and we’re looking forward to hearing from you soon.
All the best,
Thank you, it worked now! I appreciate you guys being responsive to this.
There are some other API calls that I’ll be needing which don’t seem to work properly with shared drives as well. I haven’t tested them all but I’m guessing pretty much all of them other than the ones you just updated.
Are there plans to extend this support to them?
For example, I’m able to create a file no problem because it creates it in the service account’s virtual drive, but I can’t move that file to a folder in a shared drive.
Google drive’s API doesn’t support moving folders into shared drives, so if you can optionally specify a drive ID and parent folder in the create API call that would be ideal. That way I could create a folder inside the shared drive structure.