The Google Drive Folder Reader node enables automated content extraction from multiple files in a Google Drive folder. This node is particularly powerful for batch processing documents, images, and data files stored in Google Drive.

​
Table of Contents

​
Quick Start

Choose your approach based on your situation:
Your SituationConfigurationNext NodeExample FlowWhy This Works
Small folder, want file contentKeep default settingsFile Reader (Loop Mode)View ExampleSimple setup, gets content directly
Large folder, need speedEnable “Return Drive Links Only”Google Drive File ReaderView ExampleFast folder scan, then download files
Mixed file types (Docs, PDFs, etc.)Enable “Return Doc Links Only”Router nodeView ExampleRoutes each file type to best processor

​
Node Configuration

Google Drive Folder Reader configuration options

​
Folder Selection

Choose one method to specify your folder:
  • Select Folder: Browse and select from your Google Drive
  • Use Link: Paste a direct Google Drive folder URL

​
Core Options

​
Read All Subfolders

  • When enabled: Reads files from all nested subfolders recursively
  • When disabled: Reads only files from the selected folder
  • Performance: Can significantly increase processing time for deeply nested structures
  • Note: Not available when using the node as a trigger
Return Drive or Doc Links configuration
These options make the node run significantly faster by returning links instead of downloading the files: Return Drive Links Only
  • Output: drive.google.com links for ALL files (G Suite and non-G Suite)
  • Best for: Large folders where you want consistent link format
  • Performance: Fastest option available
Return Doc Links Only
  • Output:
    • G Suite files (Docs, Sheets, Slides): docs.google.com links
    • Non-G Suite files: drive.google.com links
  • Best for: Mixed file types requiring different processing paths
  • Performance: Fast, with automatic file type routing
Output: File objects that can be directly connected to:
✓ File Reader, PDF Reader
✓ Slack Message Sender, Gmail Sender (as attachments)
✓ AI Analyze Image, Analyze Video nodes
Note: Total folder size limit of 400 MB applies when downloading files directly. 
Output: Text links that require additional processing:
✓ Google Drive File Reader → File objects
✓ Google Docs/Sheets/Slides Reader → Content
✓ Router → Conditional processing

​
Processing Different File Types

Example Workflow: Mixed File Type Processing Why this works:
  • Speed: Scanning folder returns links instantly
  • Efficiency: Each file type uses its optimal reader
  • Scalability: Handles hundreds of files efficiently

​
Method 2: Direct File Processing (Simpler Setup)

Example Workflow: Direct File Processing When to use:
  • Small to medium folders (under 400 MB total size)
  • Mixed file types that you want to process uniformly
  • Quick prototyping and testing
Important Setup Note: When connecting Google Drive Folder Reader to File Reader:
  1. Do NOT enable “Use Link” on the File Reader node
  2. Do enable “file” as an input in the File Reader’s “Configure Inputs” section
  3. The connection should pass file objects, not links
Note: File Reader now supports Google Docs, Sheets, and Slides when connected directly with the Drive Folder Reader node, but specialized nodes (Google Docs Reader, Google Sheets Reader, etc.) provide better performance and more features.

​
Example Workflows

​
1. Enterprise Document Analysis

Google Drive Folder Reader (Return Doc Links Only)
→ Router (file type detection)
→ Specialized Readers (Docs/Sheets/PDF)
→ Extract Data
→ Airtable Writer

Purpose: Process quarterly reports across multiple departments

​
2. Student Assignment Processing

Google Drive Folder Reader (Read All Subfolders enabled)
→ File Reader (Loop Mode)
→ Ask AI (plagiarism check)
→ Google Sheets Writer

Purpose: Batch process assignments from multiple class folders

​
3. Fast File Distribution

Google Drive Folder Reader (Return Drive Links Only)
→ Google Drive File Reader (Loop Mode)
→ Slack Message Sender

Purpose: Share new files with team members efficiently

​
4. Invoice Processing Pipeline

Google Drive Folder Reader
→ PDF Reader (Loop Mode)
→ Extract Data (invoice details)
→ Categorizer (by vendor)
→ Notion Database Writer

Purpose: Automate accounts payable document processing

​
Trigger Functionality

The node can automatically start your flow when new files are added to the folder.
Google Drive Folder Reader as trigger
Only monitors the selected top-level folder.
Learn more: Triggers Documentation

​
Best Practices

​
Performance Optimization

  1. Large folders: Always enable link return options
  2. Mixed file types: Use “Return Doc Links Only” with Router
  3. Uniform processing: Use File Reader for simple content extraction
  4. Specialized needs: Use dedicated nodes (Google Docs Reader, PDF Reader, etc.)

​
File Type Strategy

File Types in FolderRecommended ApproachConfiguration
All PDFsDirect processingDefault → PDF Reader
All G Suite filesSpecialized readersReturn Doc Links → Native readers (ie. Doc Reader, Slides Reader, etc)
Mixed typesRouter-based processingReturn Doc Links → Router
Large volumeLink-based processingReturn Drive Links → Loop processing → Drive File Reader → File Reader

​
Important Considerations

Authentication
  • Requires Google Drive authentication via Credentials page
  • Must have access to the target folder
Performance
  • Link options significantly improve speed for large folders
  • Subfolder reading can increase processing time exponentially
Limitations
  • Very large folders (100+ files) may timeout without link options. Make sure to enable Return Drive Links or Return Doc Links under Show More Options in such cases.
  • Total folder size limit: 400 MB. Folders exceeding this total size limit will fail during processing.
In summary, the Google Drive Folder Reader is a versatile node that adapts to different use cases through its configuration options. For best results, choose your configuration based on folder size, file types, and processing requirements.