How to Integrate Google Drive with Titan Flow

Overview 

The Google Drive node in Titan Flow allows you to automatically upload files to Google Drive as part of an automated workflow. 

Instead of manually downloading and re-uploading documents between systems, Titan Flow manages file storage within the automation sequence. Files generated or collected during the Flow can be uploaded to a specific Google Drive folder and used in downstream steps. 

This ensures structured storage, reduced manual effort, and consistent document handling across processes. 

Titan Solution

The Google Drive integration enables Titan Flow to upload one or multiple files to a designated Google Drive folder during Flow execution. 

You can: 

• Upload single or multiple files 
• Dynamically define the destination folder
• Capture and store the Google Drive file link in a Flow variable 
• Continue the Flow with actions such as email distribution or Salesforce updates

The upload becomes part of your automation logic, eliminating manual storage steps. 

When to Use the Google Drive Node 

Use this integration when you need to:

• Automatically store generated documents in Google Drive
• Upload user-submitted files from a web project
• Centralize document storage outside Salesforce
• Capture a Google Drive link for use in later Flow steps

Prerequisites

Before configuring the Google Drive node:

• Authenticate your Google Drive account inside Titan
• Ensure required files exist as Flow file variables or document templates

How to Configure the Google Drive Node

Step 1: Add the Google Drive Node

1. Click the + icon in your Flow.
2. The Add Node screen opens.
3. Select the Integrations tab.
4. Click Google Drive.
5. Click Next.

The Add Node / Google Drive configuration screen opens.

Step 2: Configure Folder Selection

Under the Folder selection method, choose one of the following:

Option A: Folder ID (Recommended)

This method uses the unique Google Drive folder ID.

You can configure it as:

• Static
  Enter the folder ID manually.
  The folder ID is the alphanumeric string in the URL:

drive.google.com/drive/folders/1KhL4Gkv9zUUl2dMl_xxxQp0MuygRqm-zh

• Field
  Select a project variable that contains the folder ID.

Option B: Folder Name

This method selects or creates a folder by name.

You can configure it as:

Static
Enter the folder name manually.

Field
Select a project variable that contains the folder name.

Important:

If a folder with the same name already exists in Google Drive but was not created through the Titan API, Titan cannot access it. In this case, Titan will create a new folder with the same name and upload files there.

Note: Google Drive allows multiple folders with the same name in the same location.

Step 3: Select Files to Upload

Use the Files to upload dropdown to select the files variable(s) that contain the files you want to upload. 

These variables store files generated or collected earlier in the Flow, such as files uploaded through a form, generated documents, or files returned by other nodes.

Step 4: Store the File URL

Use the Store link to dropdown to select a static variable.

The uploaded file URL will be stored in this variable for later use in the Flow.

Step 5: Finalize the Node

1. Click Next.
2. Enter a value in the Tag field.
   This label will appear on the Flow canvas.
3. Click Insert.

The Google Drive node is now added to your Flow.

Result

When the Flow runs:

• The selected document is uploaded to Google Drive
• The file is stored in the configured folder
• The file URL is returned to the selected project variable
• The Flow continues with the stored link available for further actions

Notes

• Authentication is required before using the Google Drive node.
• Folder ID provides more reliable targeting than folder name.
• Google Drive allows duplicate folder names in the same location, which may result in unintended uploads when using Folder Name.
• The node uploads files only and does not modify existing files.
• During Google authentication, Titan is granted API-level access with a restricted scope.
• When using Folder Name, Titan may not detect manually created folders in Google Drive. In this case, Titan may create a new folder with the same name during Flow execution.
• Existing folders can still be accessed by providing the Folder ID directly.