Skip to main content
The Google Drive connector uploads to and downloads from the Google Drive cloud storage service.

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 Arc flow are uploaded to the upload target folder, and files found in the download target folder are downloaded and entered into the Arc 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 Arc 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 Arc 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.

Arc automatically cleans up the resource cache. This process runs in the background during every receive cycle and removes stale cache entries for files that are no longer present on the remote server. This keeps the cache size manageable without requiring any manual action.

By default, files are retained for 30 days, but you can use the ResourceCacheRetentionDays setting in the Other Settings field on the Advanced tab to adjust it to fit your environment. For example, ResourceCacheRetentionDays=15 retains files for 15 days before removing them.

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

These are a collection of settings that identify and authenticate to the proxy through which the connection should be routed. By default, this section uses the global settings on the Proxy Settings portion of the Security Settings page. Clear the checkbox to supply settings specific to your connector.

SettingDescription
Proxy TypeThe protocol used by a proxy-based firewall.
Proxy HostThe name or IP address of a proxy-based firewall.
Proxy PortThe TCP port for a proxy-based firewall.
Proxy UserThe user name to use to authenticate with a proxy-based firewall.
Proxy PasswordA password used to authenticate to a proxy-based firewall.
Authentication SchemeLeave the default None or choose from one of the following authentication schemes: Basic, Digest, Proprietary, or NTLM.

Logging

Settings that govern the creation and storage of logs.

SettingDescription
Log LevelThe verbosity of logs generated by the connector. When you request support, set this to Debug.
Log Subfolder SchemeInstructs the connector to group files in the Logs folder according to the selected interval. The Weekly option (which is the default) instructs the connector to create a new subfolder each week and store all logs for the week in that folder. Leaving this setting blank tells the connector to save all logs directly in the Logs folder. For connectors that process many transactions, using subfolders helps keep logs organized and improves performance.
Log MessagesCheck this to have the log entry for a processed file include a copy of the file itself. If you disable this, you might not be able to download a copy of the file from the Transactions tab.

Miscellaneous

Miscellaneous settings are for specific use cases.

SettingDescription
Other SettingsEnables you to configure hidden connector settings in a semicolon-separated list (for example, setting1=value1;setting2=value2). Normal connector use cases and functionality should not require the use of these settings.

Automation Tab

Automation Settings

Settings related to the automatic processing of files by the connector.

Automation Status

Performance

Settings related to the allocation of resources to the connector.

SettingDescription
Max WorkersThe maximum number of worker threads consumed from the threadpool to process files on this connector. If set, this overrides the default setting on the Performance Settings portion of the Advanced Settings page.
Max FilesThe maximum number of files sent by each thread assigned to the connector. If set, this overrides the default setting on the Performance Settings portion of the Advanced Settings page.

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
Google might require an OAuth callback/redirect URL when generating OAuth credentials. The Arc 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 Arc 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.
After configuration is complete, files placed in the connector Transactions tab are uploaded to the remote storage. If Send Automation is enabled, the upload happens automatically; otherwise, you can send individual files from the Transactions tab.

Download

To download files, set the Remote Folder field in the Receive portion of the Settings page to the folder where files should be downloaded. Use a comma-delimited list to specify multiple folders. Use the File Mask to set a glob filter (for example *.txt) that limits the downloads to files matching the filter. To specify multiple filters, use the Receive Filter option on the Advanced tab. Use Delete to specify whether successfully downloaded files should be removed from the remote storage. After configuration is complete, files are downloaded according to the Receive Automation settings, or you can manually click the Receive button on the Transactions tab.

Macros

Examples