Google Drive Node

Overview

The Google Drive Node is a file synchronization and management component that automates fetching and synchronizing files from Google Drive and supports action-based operations for creating, editing, and managing docs and folders. As a Batch Trigger, it supports various file types including Google Docs, Slides, Word Documents, PDFs, and text files for vectorization and indexing in RAG flows. As an Action node, it lets you create Google Docs, edit files, create folders, list files, move files, and get file metadata.

This node is a Batch Trigger node that streamlines file collection from Google Drive and prepares files for vectorization and indexing to enhance RAG flows. It also supports Action mode for direct operations on Google Drive (create doc, edit file, create folder, list files, move file, get file metadata).

Features

Prerequisites

Before using Google Drive Node, ensure the following:

• Google Drive Credentials: Valid Google authentication details for accessing the desired folder.
• Target Folder URL: The specific Google Drive folder URL from which files will be fetched.
• Cron Expression Knowledge: Understanding of Cron expressions for scheduling flows.
• RAG Flow Setup: A separate flow configured for implementing Retrieval-Augmented Generation.

Setup

Step 1: Set Up Google Drive Access

1. Create Google Drive Credentials:

   • Set up Google OAuth credentials for Drive API access
   • Ensure proper permissions for the target folder
   • Test folder accessibility and file permissions

2. Identify Target Folder:

   • Copy the Google Drive folder URL
   • Verify folder contains supported file types
   • Ensure folder is accessible with provided credentials

Step 2: Configure Google Drive Credentials

Use the following format to set up your credentials:

Step 3: Set Up Lamatic Flow

1. For Batch Trigger: Create a custom flow for Google Drive:

   • Configure the Google Drive node as trigger
   • Set up scheduling parameters
   • Define synchronization preferences

2. For Action Node: Add the Google Drive node as an action in your flow:

   • Set up Google Drive credentials
   • Select the desired action (Create Google Doc, Edit File, Create Folder, List files, Move File, Get File Metadata)
   • Configure action-specific parameters

3. Use Pre-built Usecases from the Lamatic Studio

Configuration Reference

Batch Trigger Configuration

Action Node Configuration

Configure the Google Drive node as an action by selecting the desired action and providing the required parameters.

Available Actions

1. Create Google Doc

Creates a new Google Doc. Markdown content is converted to DOCX and uploaded to Drive.

2. Edit File

Updates an existing file. Markdown content is converted to DOCX; the existing file is replaced with the new DOCX.

3. Create Folder

Creates a new folder in Google Drive.

4. List files in Folder

Lists files in a specified folder.

5. Move File

Moves a file to a different folder.

6. Get File Metadata

Fetches metadata for a specific file.

Low-Code Example

Batch Trigger Example

triggerNode:
  nodeId: triggerNode_1
  nodeType: googleDriveNode
  nodeName: Google Drive
  values:
    process: batch
    syncMode: incremental_append
    credentials: Google Drive OAuth
    cronExpression: 0 0 */12 ? * * UTC
    folderUrl: https://drive.google.com/drive/folders/YOUR_ID

Action Node Example

- nodeId: googleDriveNode_1
  nodeType: googleDriveNode
  nodeName: Google Drive
  values:
    credentials: Google Drive OAuth
    action: createGoogleDoc  # or editFile, createFolder, listFiles, moveFile, getFileMetadata
    documentTitle: ''
    parentFolder: ''
    initialContentMarkdown: ''
    folder: ''
    file: ''
    contentMarkdown: ''
    folderName: ''
    pageSize: 100
    destinationFolder: ''
  needs:
    - triggerNode_1

Testing

For testing purposes, you need to manually provide content and document_key as dummy data. Once deployed, these values will be automatically fetched from your configured Google Drive folder.

Test Configuration

{
    "document_key": "test_document.pdf", 
    "content": "This is test content that will be processed for RAG flows"
}

• document_key: Serves as the unique identifier for the document, used to locate or update the specific file or filename.
• content: Represents the data or text that will be stored in the document.

Output

Batch Trigger Output

• document_key: String identifier for the document (filename or unique key)
• content: String containing the document content or text data
• metadata: Additional file information (if available)
  • file_type: Type of the processed file
  • last_modified: Timestamp of last modification
  • file_size: Size of the file in bytes

Action Node Output

Action node output depends on the action performed:

• Create Google Doc: Returns the new document ID and metadata (e.g., id, name, webViewLink).
• Edit File: Returns updated file metadata.
• Create Folder: Returns the new folder ID and metadata.
• List files in Folder: Returns a list of files with id, name, mimeType, and related metadata; length limited by Page Size.
• Move File: Returns updated file metadata including new parent folder.
• Get File Metadata: Returns file metadata (e.g., id, name, mimeType, size, createdTime, modifiedTime).

Troubleshooting

Common Issues

Debugging

• Check Lamatic Flow logs for detailed error messages
• Verify Google Drive API access permissions
• Test the folder URL to ensure it's valid and accessible
• Validate Cron expression syntax using online Cron validators
• Monitor file processing logs for specific file errors
• Test with a small folder containing few files before scaling up
• Verify network connectivity and API rate limits

Additional Resources

• Google Drive API Documentation (opens in a new tab)
• Cron Expression Generator (opens in a new tab)
• Google OAuth Setup Guide (opens in a new tab)