Key Capabilities
- OAuth-based Google Drive integration with automatic token management
- Support for Google Workspace document export in multiple formats (Docs, Sheets, Slides)
- Configurable send and receive scopes for different Google Drive areas
- Advanced file filtering and recursive directory operations
- Optional caching to ensure only new or updated files are downloaded
Overview
Each Google Drive connector connects to a specific Google Drive storage account. Within the remote storage, you set a single folder as the upload target, but you can use a comma-separated list to supply multiple download targets. Files that reach the Google Drive connector in the flow are uploaded to the upload target folder, and files found in the download target folder are downloaded and entered into the flow. The connector supports upload and download filters to send and receive only specific file names and/or file extensions. Account authentication uses OAuth, so you must enter account credentials in an external site portal the first time the connector connects. The external portal generates an OAuth token that the connector uses to connect, then the connector handles token refresh automatically.Connector Configuration
This section contains all of the configurable connector properties.Settings Tab
Authorization
Settings related to authorizing access to the remote storage.Google might require an OAuth callback/redirect URL when generating OAuth credentials. The callback/redirect URL is the same as the address and port where the application is hosted, plus the following resource path:
src/oauthCallback.rst. For example, if is hosted on ‘mydomain.com’ on port 8001, specify the following URL as the callback/redirect URL: http://mydomain.com:8001/src/oauthCallback.rst.Send
Settings related to uploading to the remote storage.When you upload to a shared drive where the authenticated account is a contributor (not an owner or organizer), the Overwrite remote files feature is not supported. This is a limitation imposed by Google’s Drive API permission model.
Receive
Settings related to downloading from the remote storage.Caching
Settings related to caching and comparing files between multiple downloads. When you enable caching, the file names are case-insensitive. For example, the connector cannot distinguish between
TEST.TXT and test.txt.Advanced Tab
Advanced Settings
Settings not included in the previous categories.Proxy Settings
Logging
Miscellaneous
Automation Tab
Automation Settings
Settings related to the automatic processing of files by the connector.Performance
Alerts Tab
SLAs Tab
Establishing a Connection
OAuth credentials are required to establish a connection with the Google Drive connector. Acquire the OAuth credentials from Google via the Google Console, then specify them in the following connector fields on the Settings tab:- OAuth Client ID
- OAuth Client Secret
src/oauthCallback.rst. For example, if is hosted on ‘mydomain.com’ on port 8001, specify the following URL as the callback/redirect URL: http://mydomain.com:8001/src/oauthCallback.rst.
Once authentication is successfully completed with Google, the Google Drive connector handles refreshing the OAuth tokens to ensure that authentication persists over time.
Uploading and Downloading
Upload
To upload files, set the Remote Folder field in the Send portion of the Settings page to the folder where files should be uploaded. Each Google Drive connector uploads to a single folder location. Use the Overwrite remote files option to indicate whether files that already exist in the remote folder should be overwritten or skipped.When you upload to a shared drive where the authenticated account is a contributor (not an owner or organizer), the Overwrite remote files feature is not supported. This is a limitation imposed by Google’s Drive API permission model.