What is googlecalendar-automation?

An automation flow for Google Calendar operations using Composio's Google Calendar toolkit via Rube MCP.

Do I always need to search tools first?

Yes. RUBE_SEARCH_TOOLS returns current tool schemas; hardcoding slugs or args is discouraged.

How do I execute a workflow end-to-end?

Add the MCP endpoint, verify tools with RUBE_SEARCH_TOOLS, ensure the googlecalendar connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then run RUBE_MULTI_EXECUTE_TOOL with memory and a session_id.

googlecalendar-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/googlecalendar-automation --openclaw

Files (1)

SKILL.md

3.0 KB

Google Calendar Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/googlecalendar

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Google Calendar connection via RUBE_MANAGE_CONNECTIONS with toolkit googlecalendar
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 googlecalendar
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 Calendar 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 Calendar task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["googlecalendar"]
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 Calendar-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `googlecalendar`
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`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/googlecalendar-automation/SKILL.md

View on GitHub

Overview

Automate Google Calendar operations through Composio's Google Calendar toolkit via Rube MCP. It emphasizes discovering current tool schemas before execution and ensuring an active connection. This enables resilient, schema-aware calendar workflows that adapt to tool changes.

How This Skill Works

Tools are discovered with RUBE_SEARCH_TOOLS to fetch current schemas. Next, connect or verify the googlecalendar toolkit using RUBE_MANAGE_CONNECTIONS. Finally, run the selected tool with RUBE_MULTI_EXECUTE_TOOL, always including a memory payload and a session_id to support multi-step workflows.

When to Use It

Automate creation, updates, or deletions of Google Calendar events.
Build workflows that adapt to changing tool schemas by always running RUBE_SEARCH_TOOLS first.
Verify that the Google Calendar connection is ACTIVE before executing any tools.
Run multi-tool workflows that reuse session IDs and pass a memory payload.
Handle large calendars or paginated responses by continuing to fetch tool results until complete.

Quick Start

Step 1: Add Rube MCP endpoint https://rube.app/mcp and verify RUBE_SEARCH_TOOLS responds.
Step 2: Run RUBE_MANAGE_CONNECTIONS for toolkit googlecalendar and complete authentication if prompted.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before selecting tools.
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE status.
Use exact field names and types from tool schemas returned by search.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if {}).
Reuse session IDs within a workflow and paginate results as needed.

Example Use Cases

Create a recurring team meeting and automatically invite participants.
Adjust event times when a project deadline shifts and notify attendees.
Pull all events within a date range and generate a concise summary report.
Delete cancelled events and archive relevant details for audit.
Bulk-create events from an external list using a guided discovery workflow.

Frequently Asked Questions

Add this skill to your agents