Google Drive integration

Cloud Infrastructure · 16 actions · OAuth or Bearer token auth

Google Workspace integration: Drive (files/folders), Docs, Sheets, and Slides via the v3 / v1 REST APIs.

Put Google Drive to work View Google Drive integration docs

Overview

The ModuleX Google Drive integration lets a ModuleX agent operate Google Drive on your behalf — running create and update actions across text files, folders and google docs — directly from a plain-English request, using your organization's own Google Drive credentials. No pre-built workflow is required: the agent picks the right Google Drive action for the task.

Google Drive is a cloud infrastructure platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Google Drive action — or, when you want a repeatable process, the composer assembles a Google Drive workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Google Drive in plain English

Type what you want. A ModuleX agent picks the right Google Drive action — or chains several — and runs it. No workflow to build.

Create a plain text (.txt) or markdown (.md) file via multipart upload
resolves tocreate_text_file
Find the google doc I describe and update it
resolves toread_google_docupdate_google_doc
Replace a text file's content via media upload; optionally rename in a follow-up call
resolves toupdate_text_file
Show me the google sheets that match what I describe
resolves toread_google_sheet

Use cases

What you can automate with Google Drive

Find the right google doc and update it in one promptread_google_docupdate_google_doc
Create a text file straight from a requestcreate_text_file
Update a google sheet the moment something changesupdate_google_sheet
Add a slide on the flyadd_slide

At a glance

Google Drive integration at a glance

VendorGoogle Drive

CategoryCloud Infrastructure

Actions available16

AuthenticationOAuth or Bearer token

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

All 16 Google Drive actions

Text Files2

create_text_file

Create a plain text (.txt) or markdown (.md) file via multipart upload

update_text_file

Replace a text file's content via media upload; optionally rename in a follow-up call

Folders1

create_folder

Create a folder

Google Docs3

create_google_doc

Create a Google Doc (Drive create + optional Docs batchUpdate to insert content)

read_google_doc

Read full text content from a Google Doc

update_google_doc

Replace all content (read end-index, deleteContentRange, insertText)

To Google Docs1

append_to_google_doc

Append content at the end of a doc

Google Sheets3

create_google_sheet

Create a Sheet (Sheets API create + optional Drive PATCH to move + optional Sheets API values write)

read_google_sheet

Read values from a range (resolves localized sheet name via /spreadsheets?fields=sheets.properties.title)

update_google_sheet

PUT values into an A1 range

Format Sheet Cells1

format_sheet_cells

Format cells (background color + horizontal/vertical alignment) — converts A1 to GridRange

Format Sheet Texts1

format_sheet_text

Format text in cells (bold/italic/font_size/color)

Google Slides2

create_google_slides

Create a blank Slides presentation (+ optional move)

read_google_slides

Read slide metadata + extract text + placeholder IDs from each slide

Slides1

add_slide

Add a slide with the given predefined layout

Slide Contents1

update_slide_content

Replace text in a slide placeholder (deleteText ALL + insertText 0)

See full parameters and response schemas in the Google Drive integration docs

Two ways

Two ways to use Google Drive in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Google Drive action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires Google Drive into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting Google Drive

OAuthGoogle Drive uses OAuth. You connect your Google Drive account once; ModuleX stores the access token encrypted and scoped to your organization, so your team shares a single secure connection.

Bearer tokenGoogle Drive uses bearer-token authentication. You provide a Google Drive access token; ModuleX encrypts it and scopes it to your organization so the whole team can use Google Drive.

Step-by-step setup in the Google Drive docs

Pairs well with Google Drive

Agents often chain Google Drive with these — connect them once and the agent can use all of them in a single task.

Amazon Web Services21 actions

Dropbox12 actions

Google Cloud11 actions

Microsoft OneDrive11 actions

GoDaddy5 actions

Azure Storage4 actions

FAQ

Google Drive + ModuleX FAQ

A ModuleX agent can run any of Google Drive's 16 actions — across text files, folders, google docs and google sheets — from a plain-English request, using your organization's own Google Drive credentials.

No. The agent selects the right Google Drive action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

Through OAuth — you connect your Google Drive account once and ModuleX stores the token encrypted, scoped to your organization.

16, spanning text files, folders, google docs and google sheets.

Google Drive runs on your own credentials, so any Google Drive usage is billed by Google Drive directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Google Drive to work in ModuleX.

Connect Google Drive once with your own credentials and let your agent run all 16 actions on demand.

Put Google Drive to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →