Google Drive
Search and read Google Drive file metadata, export Google Docs text, create folders, rename or move files, and work with comments, permissions and revisions.
Organise shared documents automatically and feed document text into search, review and AI flows.
Source actions
8
Destination actions
4
Data types
9
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
about
- Get accountSource
The authorised user and storage quota.
comments
- Add file commentDestinationNot retried automatically
Adds an unanchored comment to a file.
- List file commentsSourceIncremental
Comments and replies on a file, optionally modified since a time.
drives
- List shared drivesSource
Shared drives the user is a member of.
file text
- Export document textSource
Exports a Google Doc or Slides file as plain text, or a Google Sheet's first sheet as CSV.
files
- Get file metadataSource
Metadata for one file or folder.
- Search filesSourceIncremental
Files and folders by folder, name, type, full text and modified time. Metadata only; excludes trash by default.
- Rename or move fileDestinationDuplicate protected
Renames a file or folder, changes its description or star, or moves it between folders.
folders
- Create folderDestinationNot retried automatically
Creates a folder, optionally inside a parent folder or shared drive.
permissions
- List file permissionsSource
Who can access a file and with which role.
replies
- Reply to file commentDestinationNot retried automatically
Replies to a comment, optionally resolving or reopening it.
revisions
- List file revisionsSource
Revision history metadata for a file.
Authentication
Google OAuth client and refresh token
Plans and access
Personal Google accounts and all Google Workspace editions. Requires a Google Cloud OAuth client. Restricted Drive scopes need Google verification for external users.
Test environment
Use a test Google account and an OAuth client in testing mode.
Rate limits
Per-project and per-user query quotas (about 12,000 queries per minute per user); HTTP 403/429 rate-limit errors with exponential backoff.
Provider events
Drive push notifications (changes.watch / files.watch channels). Nexra event triggers are not yet available; flows run on demand or on a schedule.
Before you build a flow
- Binary file uploads and downloads are not implemented; only metadata and Google Docs text export are read.
- Export is bounded by Google's 10 MB export limit and Nexra's 5 MB response limit; text is truncated to the requested length.
- Trashing, deleting and sharing (permission changes) are not implemented; permissions are read-only.
- Folder creation and comments have no idempotency key; uncertain writes are not repeated automatically.
- Drive reports some rate limits as HTTP 403 userRateLimitExceeded, which Nexra classifies as a permission error.