Google Calendar Automation

# Google Calendar Automation via Rube MCP

Automate Google Calendar workflows including event creation, scheduling, availability checks, attendee management, and calendar browsing through Composio's Google Calendar toolkit.

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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds

2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googlecalendar`

3. If connection is not ACTIVE, follow the returned auth link to complete Google OAuth

4. Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. Create and Manage Events

**When to use**: User wants to create, update, or delete calendar events

**Tool sequence**:

1. `GOOGLECALENDAR_LIST_CALENDARS` - Identify target calendar ID [Prerequisite]

2. `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` - Get current time with proper timezone [Optional]

3. `GOOGLECALENDAR_FIND_FREE_SLOTS` - Check availability before booking [Optional]

4. `GOOGLECALENDAR_CREATE_EVENT` - Create the event [Required]

5. `GOOGLECALENDAR_PATCH_EVENT` - Update specific fields of an existing event [Alternative]

6. `GOOGLECALENDAR_UPDATE_EVENT` - Full replacement update of an event [Alternative]

7. `GOOGLECALENDAR_DELETE_EVENT` - Delete an event [Optional]

**Key parameters**:

- `calendar_id`: Use 'primary' for main calendar, or specific calendar ID

- `start_datetime`: ISO 8601 format 'YYYY-MM-DDTHH:MM:SS' (NOT natural language)

- `timezone`: IANA timezone name (e.g., 'America/New_York', NOT 'EST' or 'PST')

- `event_duration_hour`: Hours (0+)

- `event_duration_minutes`: Minutes (0-59 only; NEVER use 60+)

- `summary`: Event title

- `attendees`: Array of email addresses (NOT names)

- `location`: Free-form text for event location

**Pitfalls**:

- `start_datetime` must be ISO 8601; natural language like 'tomorrow' is rejected

- `event_duration_minutes` max is 59; use `event_duration_hour=1` instead of `event_duration_minutes=60`

- `timezone` must be IANA identifier; abbreviations like 'EST', 'PST' are NOT valid

- `attendees` only accepts email addresses, not names; resolve names first

- Google Meet link creation defaults to true; may fail on personal Gmail accounts (graceful fallback)

- Organizer is auto-added as attendee unless `exclude_organizer=true`

2. List and Search Events

**When to use**: User wants to find or browse events on their calendar

**Tool sequence**:

1. `GOOGLECALENDAR_LIST_CALENDARS` - Get available calendars [Prerequisite]

2. `GOOGLECALENDAR_FIND_EVENT` - Search by title/keyword with time bounds [Required]

3. `GOOGLECALENDAR_EVENTS_LIST` - List events in a time range [Alternative]

4. `GOOGLECALENDAR_EVENTS_INSTANCES` - List instances of a recurring event [Optional]

**Key parameters**:

- `query` / `q`: Free-text search (matches summary, description, location, attendees)

- `timeMin`: Lower bound (RFC3339 with timezone offset, e.g., '2024-01-01T00:00:00-08:00')

- `timeMax`: Upper bound (RFC3339 with timezone offset)

- `singleEvents`: true to expand recurring events into instances

- `orderBy`: 'startTime' (requires singleEvents=true) or 'updated'

- `maxResults`: Results per page (max 2500)

**Pitfalls**:

- **Timezone warning**: UTC timestamps (ending in 'Z') don't align with local dates; use local timezone offsets instead

- Example: '2026-01-19T00:00:00Z' covers 2026-01-18 4pm to 2026-01-19 4pm in PST

- Omitting `timeMin`/`timeMax` scans the full calendar and can be slow

- `pageToken` in response means more results; paginate until absent

- `orderBy='startTime'` requires `singleEvents=true`

3. Manage Attendees and Invitations

**When to use**: User wants to a