Google Drive

Google Drive

Google Drive

Access Google Drive via the Google Drive API with managed OAuth authentication. Search files, manage permissions, organize folders, upload and download, and handle sharing changes.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure Google Drive API access yourself.

Setup in 3 Steps

How It Works

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│   Google Drive   │
│   (User Chat)   │     │   (OAuth)    │     │   (Drive API)    │
└─────────────────┘     └──────────────┘     └──────────────────┘
         │                       │                       │
         │  1. Install Plugin    │                       │
         │  2. Pair Device       │                       │
         │  3. Connect Drive     │                       │
         │                       │  4. Secure Token       │
         │                       │  5. Proxy Requests    │
         │                       │                       │
         ▼                       ▼                       ▼
   ┌──────────┐           ┌──────────┐           ┌──────────┐
   │  SKILL   │           │ Dashboard│           │  Google  │
   │  File    │           │ Auth     │           │  Drive   │
   └──────────┘           └──────────┘           └──────────┘

Install

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for Google Drive again."

Quick Start

# Find a file by name
clawlink_call_tool --tool "googledrive_find_file" --params '{"query": "report.xlsx"}'

# Get file metadata
clawlink_call_tool --tool "googledrive_get_file_metadata" --params '{"file_id": "YOUR_FILE_ID"}'

# List permissions
clawlink_call_tool --tool "googledrive_list_permissions" --params '{"file_id": "YOUR_FILE_ID"}'

Authentication

All Google Drive tool calls are authenticated automatically by ClawLink using the user's connected Google account.

No API key is required in chat. ClawLink stores the OAuth token securely and injects it into every Google Drive API request on the user's behalf.

Getting Connected

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with clawlink_begin_pairing if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=google-drive and connect Google Drive.
4. Call clawlink_list_integrations to verify the connection is active.

Connection Management

List Connections

clawlink_list_integrations

Response: Returns all connected integrations. Look for google-drive in the list.

Verify Connection

clawlink_list_tools --integration google-drive

Response: Returns the live tool catalog for Google Drive.

Reconnect

If Google Drive tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=google-drive
2. After they confirm, call clawlink_list_integrations to verify
3. Then call clawlink_list_tools --integration google-drive

Security & Permissions

• Access is scoped to files and folders within the connected Google account (My Drive and shared drives).
• All write operations require explicit user confirmation. Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
• Destructive actions (delete, empty trash, delete permission) are marked as high-impact and must be confirmed.
• Permission changes may have a brief propagation delay before appearing in results.

Tool Reference

File & Folder Discovery

File Creation & Upload

Download & Export

File Organization

File Metadata & Properties

Permissions & Sharing

Comments & Replies

Shared Drives

Revision Management

Trash & Deletion

Change Tracking

Utility

Code Examples

Search for files by name

clawlink_call_tool --tool "googledrive_find_file" \
  --params '{
    "query": "name contains '\''report'\''"
  }'

Create a folder

clawlink_call_tool --tool "googledrive_create_folder" \
  --params '{
    "name": "Project Files",
    "parent_folder_id": "YOUR_FOLDER_ID"
  }'

Share a file with someone

clawlink_call_tool --tool "googledrive_create_permission" \
  --params '{
    "file_id": "YOUR_FILE_ID",
    "type": "user",
    "email": "colleague@example.com",
    "role": "writer",
    "pending_owner": false
  }'

Move a file to a folder

clawlink_call_tool --tool "googledrive_move_file" \
  --params '{
    "file_id": "YOUR_FILE_ID",
    "add_parents": ["DESTINATION_FOLDER_ID"],
    "remove_parents": ["SOURCE_FOLDER_ID"]
  }'

Download and export a Google Sheet as CSV

clawlink_call_tool --tool "googledrive_download_file" \
  --params '{
    "file_id": "YOUR_SHEET_ID",
    "mime_type": "text/csv"
  }'

Trash a file

clawlink_call_tool --tool "googledrive_trash_file" \
  --params '{
    "file_id": "YOUR_FILE_ID"
  }'

Discovery Workflow

1. Call clawlink_list_integrations to confirm Google Drive is connected.
2. Call clawlink_list_tools --integration google-drive to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration google-drive.
5. If no Google Drive tools appear, direct the user to https://claw-link.dev/dashboard?add=google-drive.

Execution Workflow

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  find → list → get → describe → call                        │
│                                                             │
│  Example: Find file → Get metadata → Show results           │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                    │
│  describe → preview → confirm → call                        │
│                                                             │
│  Example: Describe tool → Preview changes → User approves    │
│           → Execute update                                   │
└─────────────────────────────────────────────────────────────┘

1. For unfamiliar tools, ambiguous requests, or any write action, call clawlink_describe_tool first.
2. Use the returned guidance, schema, whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
3. Prefer search, list, and metadata reads before writes.
4. For uploads, sharing updates, folder changes, or other high-impact actions, call clawlink_preview_tool first.
5. Execute with clawlink_call_tool. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

Notes

• File IDs are stable across moves — capture from list/search responses for subsequent operations.
• storageQuota in get_about reflects My Drive only, not shared drives.
• Concurrent permission operations on the same file are not supported — only the last update is applied.
• For Google Workspace native files (Docs, Sheets, Slides), use the dedicated API tools (googledocs_, googlesheets_) rather than GOOGLEDRIVE_EDIT_FILE.
• Empty trash is irreversible — always confirm with the user first.
• Newly created files are private by default — set sharing permissions afterward.

Error Handling

Troubleshooting: Tools Not Visible

1. Check that the ClawLink plugin is installed:

   openclaw plugins list
   

2. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.
3. If a fresh chat does not help, run:

   openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
   openclaw gateway restart
   

4. After restart, tell the user to send /new again and retry.

Troubleshooting: Invalid Tool Call

1. Ensure the integration slug is exactly google-drive.
2. Use clawlink_describe_tool to verify parameter names and types before calling.
3. For write operations, always call clawlink_preview_tool first.

Resources

• Google Drive API Overview
• Files Resource
• Permissions Resource
• ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=google-drive-files
• ClawLink Docs: https://docs.claw-link.dev/openclaw
• ClawLink Verification: https://claw-link.dev/verify

Related Skills

• Google Docs — For document reading and editing
• Google Sheets — For spreadsheet operations
• Google Slides — For presentation operations

---

Powered by ClawLink — an integration hub for OpenClaw

ClawLink Logo