Skip to main content

Overview

Tool Name

Purpose

The google_drive_tools integration connects your workflows to Google Drive and Google Workspace. Create and edit Sheets and Docs, manage files and folders, read and import Google Slides decks, format content, collaborate with comments, and automate updates across projects. Supports both User OAuth (recommended for interactive use) and Service Account (for automation and shared folders) authentication through Config → Connections.

Key Features & Functions

Sheets Operations

Read and write cell ranges, append data, manage tabs, apply formatting and themes, and export query results to Google Sheets.

Docs Operations

Create, read, update, and append content in Google Docs. Create formatted documents and apply text formatting.

Native Slides Reads

Read Google Slides decks directly through the Slides API, preserve notes and structure, summarize decks, and import them into Genesis presentation apps.

Files and Folders

List folders, get links, upload, download, move, and delete files.

Collaboration

Retrieve comments, add replies, and coordinate reviews without leaving your workflow.

Formatting

Apply cell formatting, sheet themes, conditional formatting, and format presets to Sheets. Format text in Docs.

Named Connections

Use multiple Google Workspace connections by name (e.g. shared, finance) for different teams or purposes.

Input Parameters

google_drive

Core Parameters Formatting Parameters Presentation Parameters File Parameters

Action Reference

Drive & Folder Operations

Sheets Operations

For SAVE_MULTI_QUERIES_TO_G_SHEET, each tab must name a database connection using connection_id in tabs_spec or on that tab; there is no implicit default connection. All tab queries are checked before execution; if any is not classified as READ (including UNKNOWN), the export is refused before a sheet is created, including on a dry run. Each query runs through _query_database on its selected connection. Each tab keeps up to 100000 rows; a longer result is truncated and marked truncated in that tab’s result.

Docs Operations

Presentations (Google Slides)

Comments & Collaboration

Setup & Authentication

Use Cases

  1. Google Slides understanding and import
    • Read a shared Slides URL directly, preserve speaker notes, inspect slide structure, summarize the deck, and import it into a Genesis presentation app.
  2. Stakeholder reporting
    • Run SQL queries and export results to formatted, multi-tab Sheets with themes and conditional formatting.
  3. Living project docs
    • Create formatted Docs per project, append meeting outcomes, and centralize decisions.
  4. Formatted spreadsheets
    • Apply cell formatting, themes, and conditional formatting to create polished reports.
  5. Operational runbooks
    • Keep checklists and status pages in Sheets, edited programmatically by scheduled jobs.
  6. Team reviews
    • Fetch comment threads, add replies, and resolve items from a pipeline step.
  7. Multi-connection workflows
    • Use connection_name to work with different teams’ Drive folders in the same workflow.
Deleting a file with DELETE_FILE removes it from Drive permanently. Confirm ownership, backups, and sharing expectations before proceeding.

Workflow

  1. Set up a connection
    • Create a Google Workspace connection in Config → Connections using User OAuth (recommended) or Service Account. See Google Workspace Setup.
  2. Locate or create
    • Use LIST, GET_FILE_BY_NAME, or FIND_PRESENTATIONS to find targets, or CREATE_SHEET and CREATE_DOC to start fresh.
  3. Read content
    • GET_SHEET for Sheets, READ_DOC for Docs, READ_PRESENTATION or SUMMARIZE_PRESENTATION for Slides.
    • GET_SHEET / READ_SHEET returns at most 50 rows by default. For larger sheets, either narrow g_sheet_cell to a specific range such as A1:Z200, increase max_rows, or use SAVE_SHEET_TO_FILE to export the full sheet to git and analyze it there.
  4. Edit and format
    • EDIT_SHEET, WRITE_RANGE, FORMAT_SHEET_CELLS, APPLY_SHEET_THEME for Sheets. UPDATE_DOC, CREATE_FORMATTED_DOC, FORMAT_DOC_TEXT for Docs.
  5. Export and share
    • SAVE_MULTI_QUERIES_TO_G_SHEET for SQL-to-Sheet exports. EXPORT_ALL_TABS_AS_CSV for bulk CSV export. Use comment actions for collaboration.

Integration Relevance

  • data_connector_tools to run SQL that feeds SAVE_MULTI_QUERIES_TO_G_SHEET.
  • project_manager_tools to attach Drive links to tasks and milestones.
  • artifact_manager_tools to reference generated outputs by id.
  • handoff to orchestrate spreadsheet updates as part of multi-agent routines.
  • slack_tools to distribute Drive links and comment status to channels.

Configuration Details

  • Set up connections through Config → Connections (not the legacy standalone page).
  • User OAuth is preferred for interactive use; service accounts for automation.
  • Use connection_name to select a specific connection when you have multiple.
  • Enable Google Drive API, Google Sheets API, Google Docs API, and Google Slides API in the GCP project.
  • Use A1 notation for ranges (e.g. A1, A1:B10, Sheet1!C2:D100).
  • GET_SHEET / READ_SHEET uses max_rows=50 by default. Set max_rows=0 only when you intentionally want no row cap.
  • Keep a designated shared folder for automation and set it with SET_ROOT_FOLDER.
  • Git-backed sheet export actions such as SAVE_SHEET_TO_FILE and EXPORT_ALL_TABS_AS_CSV write files using the active Genesis user context.
  • Large Google Slides decks are read in place via the Slides API; Drive export to .pptx is reserved for explicit artifact conversion.

Limitations

  1. API rate limits can throttle large batch operations. Use pagination and backoff.
  2. Very large Sheets may have write limits per call. Split updates into smaller ranges.
  3. Service account visibility depends on folder or file sharing. Share the specific deck or folder with the service account email.
  4. Native Slides extraction preserves text, notes, links, and structure, but image-heavy decks may rely on visual analysis for best results.
  5. Complex Docs formatting can vary when updated programmatically. Validate critical layouts.
  6. Concurrent edits may produce version conflicts. Serialize writes for hot files.

Output

  • File and Folder Operations
    • Listings with ids, names, mime types, and modified timestamps.
  • Sheets
    • GET_SHEET / READ_SHEET returns values, row_count, total_row_count, column_count, truncated, and tab metadata when available.
    • When a sheet response is too large for context, values is omitted and a summary with headers, preview_rows, tail_rows, and original_size_bytes is returned instead.
    • Truncated reads include a truncation_note that points you to a narrower g_sheet_cell range or SAVE_SHEET_TO_FILE for full export.
  • Docs
    • Document content snapshots, append confirmations, update results, and formatted document links.
  • Slides
    • Deck summaries, structured slide/page metadata, speaker notes, thumbnail metadata, and optional git-saved markdown/JSON artifacts.
  • Comments
    • Comment threads, new comment ids, and reply confirmations.
  • Exports
    • New Sheet id, title, and a shareable link after SAVE_MULTI_QUERIES_TO_G_SHEET.
Align permissions with your workspace policies. Use least privilege for service accounts and restrict automation to shared folders intended for data agents.