googledrive-automation

通过 Rube MCP 自动化 Google Drive 文件与文件夹管理流程

来源

GitHub

更新于

2026-06-07

// 安全评估低风险

仅提示词，不执行代码
开源可审计

正在进行安全审计…

凭证密钥
网络外发
代码执行
数据访问
来源供应链

// 安装

复制安装指令，让 AI 自动完成配置 · 推荐新手

请帮我安装 askskill 上的 "googledrive-automation" 技能：
1. 下载 https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/googledrive-automation/SKILL.md
2. 保存为 ~/.claude/skills/googledrive-automation/SKILL.md
3. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

批量整理项目文件

输入

先搜索可用的 Google Drive 工具及最新参数 schema。然后帮我把“项目A”文件夹中的 PDF 按月份移动到对应子文件夹，并把文件名统一改为“项目A-月份-原文件名”。执行前先列出计划。

预期产出

返回工具搜索结果、执行计划，以及完成后的整理与重命名结果摘要。

自动共享周报文件

输入

先搜索 Google Drive 相关工具和当前 schema。找到“周报”文件夹里最近 7 天新增的文档，批量共享给 [email protected]，权限设为可评论，并输出共享成功与失败清单。

预期产出

输出检索到的文档列表、共享操作结果，以及成功和失败的明细。

清理重复文件

输入

先搜索可用工具及 schema。扫描我的 Google Drive，找出文件名和大小相同的重复文件，按文件夹分组列出，并建议保留最新版本；未经我确认不要删除任何文件。

预期产出

生成重复文件报告、保留建议，以及待确认的清理操作列表。

// 文档

Google Drive Automation via Rube MCP

Automate Google Drive operations through Composio's Google Drive toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/googledrive

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Google Drive connection via RUBE_MANAGE_CONNECTIONS with toolkit googledrive
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit googledrive
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Google Drive operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Google Drive task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["googledrive"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Google Drive-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `googledrive`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`