I’m trying to access a shared Google Drive folder using a service account with the Google Drive Connector node, but I’m having an issue.
So far, I’ve created a Google Cloud project, enabled the Google Drive API, registered a service account, and shared the folder with the service account. After giving the Google Drive scope and successfully authenticating with the service account in the Google Authenticator node, I’m unable to find the Shared Drive folder with the Google Drive Connector (only the /My Drive folder shows). I can, however, connect to the Shared Drive folder when I use the Interactive authentication type in the Google Authenticator node with my Gmail account. Anyone have any idea on how to solve this?
Just to clarify, did you add the service account as a member of the Shared Drive itself, or just share a folder within the drive with it?
Currently, it’s not possible to access shared folders (i.e., folders shared individually) via the Google Drive Connector node. But you can access contents of Shared Drive (formerly Team Drives). We have an internal ticket open to add support for accessing shared folders (AP-17260).
Thank you, that helps, and the issue did get resolved. I do have a follow-up question: is it possible to use the string-to-path node in conjunction with a Call Workflow Service node in batch mode? I read this post (Issues when using String to Path node in batch mode - #13) which suggested it shouldn’t be, but it seems to work in my case when the path isn’t passed to a Call Workflow Service node. For example, the image below shows the result after executing in batch mode
As long as you’re not using a mountpoint-relative path (/knime/...), it generally works fine even in batch mode. The issue happens when Call Workflow Service is given a mountpoint path, because the workspace isn’t mounted by default in batch. I hope this thread gives you more context and helps you resolve it.
