Googledrive Automation

What This Skill Does

This skill automates Google Drive operations through the Composio Google Drive toolkit via Rube MCP. It allows users to programmatically manage files, folders, and permissions within Google Drive. It's designed for users who need to integrate Drive functionality into automated workflows.

When to Use

• Upload a file to Google Drive.
• Download a file from Google Drive.
• Create a new folder in Google Drive.
• Search for files by name or content.
• Manage file sharing permissions.
• Automate backups to Google Drive.

Key Features

• Connects to Google Drive via Rube MCP.
• Uses RUBE_SEARCH_TOOLS for tool discovery.
• Requires active Google Drive connection.
• Supports dynamic tool schema updates.
• Provides a core workflow pattern for execution.
• Emphasizes the importance of checking connection status.

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

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

Toolkit docs: composio.dev/toolkits/googledrive