Google Drive Release

This node applies to GlobalCapture only.

This node will need to be downloaded from the Square 9 SDN before proceeding.

The Google Drive Release node is available in the GlobalCapture nodes gallery. This node allows you to transfer files from GlobalCapture to Google Drive. All communications are performed over a secure channel, using standard networking ports.

Note: Square 9 does not sell or support Google Cloud services. If you are looking to release documents to a Google Drive destination, you will need to have an Google Workspace account available, a service account created, and credentials provisioned.

To create a Google Workspace account, refer to Google’s knowledgebase here.

This article will walk you through how to create a service account, and will provide you with the Project ID, Private Key ID, and the Private Key needed for this node’s properties.

Node Properties

Title

The title of the node should be brief but descriptive of where documents are being released. Titles are useful when reading the history in the history of a workflow for easier understanding of the overall process.

Description

Provide a synopsis of what this node is doing, or make note of any important details. This is useful for providing additional information such as where documents are being released to, why that location has been chosen, etc. A good description is helpful when returning to modify the workflow in the future.

The Client Email, Client ID and the Client Cert URL can all be found within the JSON key file downloaded from the Google service account being used.

Impersonate User

For instructions on creating a service account, refer to the documentation found here. For authentication to work, you will need to enable domain wide delegation for the service account. Documentation for enabling delegation can be found here.

The Impersonate User textbox is for configuring the email address of the google user who will need to write to the Google Drive location.

If a Team Drive is not specified, this will write to the user’s Google Drive location instead.

Team Drive ID

A Google Team Drive, now called a Shared Drive, is a shared space within Google Drive where teams can store, search, and access files. Unlike individual My Drives, files in a Shared Drive are owned by the team, not an individual, so they remain accessible even if a team member leaves. This is useful for collaborative projects and ensures team files remain accessible regardless of individual departures.

How to find the Team Drive ID

To find a Google Team Drive ID (now referred to as Shared Drive ID), navigate to the Shared Drive in Google Drive and look at the URL. The ID is the alphanumeric string following "folders/" in the URL.

For example, the URL might be https://drive.google.com/drive/folders/A1B2C3D4-E5F678H9, where "A1B2C3D4-E5F678H9" is the Shared Drive ID.

Relative Path

The Relative Path textbox specifies where we want the file to release to within the Team Drive. Specify a path or use S9 notation to create a path dynamically.

Ex. /YourPathHere

File Name

The File Name is what we want to name the file. This can be a static value, or S9 Notation can be used.

File Name should not include the extension of the file. GlobalCapture will automatically append the file name with the proper extension.

Allow overwrite of files in destination

When enabled, allow overwrite of files in destination is used to overwrite any files with the same file name, instead of creating a copy. This option is not enabled by default.

Delete Files after release

When enabled, Delete Files after release removes the files from the GlobalCapture working directory after release. This option is enabled by default.

Data Validation

Data Validation is only an option in GlobalCapture.

Data Validation

The Data Validation checkbox is enabled by default to enforce Data Types or Length settings for Fields. When enabled, if data does not meet the type or length settings for the field, the process will error on this node.

Action Select

The node expects two outputs. Success and Failure. The node can write response information from the Google Drive release to a process field if further control routing is desired.

To utilize this function, you’ll need to create a field called “Drive Status” and add this to your workflow in the process fields pane.

A Set Process Field node is not needed to use this field, as the information is automatically pulled from rclone and acts as a system field similar to Page Count, or Date Entered.

Success

Success responses:

0 - Success.

9 - Successful, but no transfer. This is the response if you are writing a file that already exists, without the overwrite option enabled.

Failure

Failure responses:

1 - Syntax error. This is an unlikely error, generally caused by incorrect parameters being passed internally.

2 - Uncategorized error.

3 - Directory not found.

4 - File not found.

5 - Temporary error - A retry step in the workflow may resolve such an error. Sometimes arising from exceeding throughput limits.

7 - Fatal error - Invalid accounts, accounts suspended, etc.

8 - Transfer limit exceeded.

Use Case

Using the Google Drive Release node for nightly uploads to a Shared Team Drive

In this example, I've configured the Google Drive Release Node to release documents to an Team Drive on a nightly basis for backup purposes. Based off of the success or failure of the release, this can redirect documents accordingly. I've also created a new process field called "Drive Status" and added this to the Process Fields pane for our workflow.

This is useful to provide an update as to whether or not the release of documents to the Team Drive have been completed or not by providing a response in the batch history.