Google Drive

Category: Productivity / Files
Connect by: Connect with OAuth
Official API docs: https://developers.google.com/workspace/drive/api/reference/rest/v3

What the agent can see

Capability	API call	Risk	Needs approval
List Drive files, optionally filtered by a Drive search query (q). (docs)	GET /drive/v3/files	🟢 low	— no
Get the full structured content of a Google Doc by document id. (docs)	GET /v1/documents/{documentId}	🟢 low	— no
Read a range of cell values from a spreadsheet (A1 notation). (docs)	GET /v4/spreadsheets/{spreadsheetId}/values/{range}	🟢 low	— no

What the agent can do

Capability	API call	Risk	Needs approval
Create a new Google Doc with a title, then insert the given body text. (docs)	POST /v1/documents (+ POST /v1/documents/{id}:batchUpdate)	🟡 medium	✅ yes
Append rows of values to the end of a sheet's table (A1 range anchor). (docs)	POST /v4/spreadsheets/{spreadsheetId}/values/{range}:append	🟡 medium	✅ yes
Write values into a specific range of a spreadsheet (overwrites cells). (docs)	PUT /v4/spreadsheets/{spreadsheetId}/values/{range}	🟡 medium	✅ yes
Create a new folder in Drive (mimeType application/vnd.google-apps.folder). (docs)	POST /drive/v3/files	🟢 low	✅ yes

Connecting it

• You provide: Google account (OAuth)
• Where to get it: Google Cloud Console → enable the Google Drive API, Google Docs API and Google Sheets API → OAuth consent screen → Credentials → Create OAuth client ID (Web application). Requested scopes: drive.file, documents, spreadsheets.
• Permissions/scopes: https://www.googleapis.com/auth/drive.file, https://www.googleapis.com/auth/documents, https://www.googleapis.com/auth/spreadsheets

Account setup

• Account needed: A Google account plus a Google Cloud project with the Drive, Docs and Sheets APIs enabled.
• App registration: Create an OAuth client ID (Web application); configure the consent screen with scopes (drive.file, documents, spreadsheets), authorized domains, and redirect URIs.
• Verification required: drive.file is a NON-sensitive, per-file scope (the app only sees files the user creates or explicitly opens with it) and avoids the RESTRICTED-scope CASA security assessment. documents and spreadsheets are SENSITIVE: production requires app verification + brand verification (no annual CASA). Broad scopes like drive (full) WOULD trigger CASA — intentionally not requested.
• Testing: Unverified 'Testing' apps are capped at 100 test users with 7-day refresh-token expiry; not shippable to production.

Limits

Per-project and per-user quotas enforced per API (Drive default ~12,000 queries/min per project, 60,000/min/user-tunable; Docs/Sheets ~300 read & 300 write req/min per project, 60/min/user). HTTP 429/403 userRateLimitExceeded on exceed — back off and retry.