google-calendar-automation
npx machina-cli add skill davepoon/buildwithclaude/google-calendar-automation --openclawGoogle 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.
Toolkit docs: composio.dev/toolkits/googlecalendar
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Google Calendar connection via
RUBE_MANAGE_CONNECTIONSwith toolkitgooglecalendar - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitgooglecalendar - If connection is not ACTIVE, follow the returned auth link to complete Google OAuth
- 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:
GOOGLECALENDAR_LIST_CALENDARS- Identify target calendar ID [Prerequisite]GOOGLECALENDAR_GET_CURRENT_DATE_TIME- Get current time with proper timezone [Optional]GOOGLECALENDAR_FIND_FREE_SLOTS- Check availability before booking [Optional]GOOGLECALENDAR_CREATE_EVENT- Create the event [Required]GOOGLECALENDAR_PATCH_EVENT- Update specific fields of an existing event [Alternative]GOOGLECALENDAR_UPDATE_EVENT- Full replacement update of an event [Alternative]GOOGLECALENDAR_DELETE_EVENT- Delete an event [Optional]
Key parameters:
calendar_id: Use 'primary' for main calendar, or specific calendar IDstart_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 titleattendees: Array of email addresses (NOT names)location: Free-form text for event location
Pitfalls:
start_datetimemust be ISO 8601; natural language like 'tomorrow' is rejectedevent_duration_minutesmax is 59; useevent_duration_hour=1instead ofevent_duration_minutes=60timezonemust be IANA identifier; abbreviations like 'EST', 'PST' are NOT validattendeesonly 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:
GOOGLECALENDAR_LIST_CALENDARS- Get available calendars [Prerequisite]GOOGLECALENDAR_FIND_EVENT- Search by title/keyword with time bounds [Required]GOOGLECALENDAR_EVENTS_LIST- List events in a time range [Alternative]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 instancesorderBy: '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/timeMaxscans the full calendar and can be slow pageTokenin response means more results; paginate until absentorderBy='startTime'requiressingleEvents=true
3. Manage Attendees and Invitations
When to use: User wants to add, remove, or update event attendees
Tool sequence:
GOOGLECALENDAR_FIND_EVENTorGOOGLECALENDAR_EVENTS_LIST- Find the event [Prerequisite]GOOGLECALENDAR_PATCH_EVENT- Add attendees (replaces entire attendees list) [Required]GOOGLECALENDAR_REMOVE_ATTENDEE- Remove a specific attendee by email [Required]
Key parameters:
event_id: Unique event identifier (opaque string, NOT the event title)attendees: Full list of attendee emails (PATCH replaces entire list)attendee_email: Email to removesend_updates: 'all', 'externalOnly', or 'none'
Pitfalls:
event_idis a technical identifier, NOT the event title; always search first to get the IDPATCH_EVENTattendees field replaces the entire list; include existing attendees to avoid removing them- Attendee names cannot be resolved; always use email addresses
- Use
GMAIL_SEARCH_PEOPLEto resolve names to emails before managing attendees
4. Check Availability and Free/Busy Status
When to use: User wants to find available time slots or check busy periods
Tool sequence:
GOOGLECALENDAR_LIST_CALENDARS- Identify calendars to check [Prerequisite]GOOGLECALENDAR_GET_CURRENT_DATE_TIME- Get current time with timezone [Optional]GOOGLECALENDAR_FIND_FREE_SLOTS- Find free intervals across calendars [Required]GOOGLECALENDAR_FREE_BUSY_QUERY- Get raw busy periods for computing gaps [Fallback]GOOGLECALENDAR_CREATE_EVENT- Book a confirmed slot [Required]
Key parameters:
items: List of calendar IDs to check (e.g., ['primary'])time_min/time_max: Query interval (defaults to current day if omitted)timezone: IANA timezone for interpreting naive timestampscalendarExpansionMax: Max calendars (1-50)groupExpansionMax: Max members per group (1-100)
Pitfalls:
- Maximum span ~90 days per Google Calendar freeBusy API limit
- Very long ranges or inaccessible calendars yield empty/invalid results
- Only calendars with at least freeBusyReader access are visible
- Free slots responses may normalize to UTC ('Z'); check offsets
GOOGLECALENDAR_FREE_BUSY_QUERYrequires RFC3339 timestamps with timezone
Common Patterns
ID Resolution
- Calendar name -> calendar_id:
GOOGLECALENDAR_LIST_CALENDARSto enumerate all calendars - Event title -> event_id:
GOOGLECALENDAR_FIND_EVENTorGOOGLECALENDAR_EVENTS_LIST - Attendee name -> email:
GMAIL_SEARCH_PEOPLE
Timezone Handling
- Always use IANA timezone identifiers (e.g., 'America/Los_Angeles')
- Use
GOOGLECALENDAR_GET_CURRENT_DATE_TIMEto get current time in user's timezone - When querying events for a local date, use timestamps with local offset, NOT UTC
- Example: '2026-01-19T00:00:00-08:00' for PST, NOT '2026-01-19T00:00:00Z'
Pagination
GOOGLECALENDAR_EVENTS_LISTreturnsnextPageToken; iterate until absentGOOGLECALENDAR_LIST_CALENDARSalso paginates; usepage_token
Known Pitfalls
- Natural language dates: NOT supported; all dates must be ISO 8601 or RFC3339
- Timezone mismatch: UTC timestamps don't align with local dates for filtering
- Duration limits:
event_duration_minutesmax 59; use hours for longer durations - IANA timezones only: 'EST', 'PST', etc. are NOT valid; use 'America/New_York'
- Event IDs are opaque: Always search to get event_id; never guess or construct
- Attendees as emails: Names cannot be used; resolve with GMAIL_SEARCH_PEOPLE
- PATCH replaces attendees: Include all desired attendees in the array, not just new ones
- Conference limitations: Google Meet may fail on personal accounts (graceful fallback)
- Rate limits: High-volume searches can trigger 403/429; throttle between calls
Quick Reference
| Task | Tool Slug | Key Params |
|---|---|---|
| List calendars | GOOGLECALENDAR_LIST_CALENDARS | max_results |
| Create event | GOOGLECALENDAR_CREATE_EVENT | start_datetime, timezone, summary |
| Update event | GOOGLECALENDAR_PATCH_EVENT | calendar_id, event_id, fields to update |
| Delete event | GOOGLECALENDAR_DELETE_EVENT | calendar_id, event_id |
| Search events | GOOGLECALENDAR_FIND_EVENT | query, timeMin, timeMax |
| List events | GOOGLECALENDAR_EVENTS_LIST | calendarId, timeMin, timeMax |
| Recurring instances | GOOGLECALENDAR_EVENTS_INSTANCES | calendarId, eventId |
| Find free slots | GOOGLECALENDAR_FIND_FREE_SLOTS | items, time_min, time_max, timezone |
| Free/busy query | GOOGLECALENDAR_FREE_BUSY_QUERY | timeMin, timeMax, items |
| Remove attendee | GOOGLECALENDAR_REMOVE_ATTENDEE | event_id, attendee_email |
| Get current time | GOOGLECALENDAR_GET_CURRENT_DATE_TIME | timezone |
| Get calendar | GOOGLECALENDAR_GET_CALENDAR | calendar_id |
Powered by Composio
Source
git clone https://github.com/davepoon/buildwithclaude/blob/main/plugins/all-skills/skills/google-calendar-automation/SKILL.mdView on GitHub Overview
Automates Google Calendar workflows using Rube MCP and Composio's googlecalendar toolkit. Create, update, and delete events; check availability; manage attendees; and browse calendars programmatically.
How This Skill Works
Connect Rube MCP to Google Calendar and ensure an ACTIVE calendar connection. Then execute a sequence of toolkit actions (list calendars, get current date/time, find free slots, create/update/delete events, and manage attendees) driven by structured parameters.
When to Use It
- When you need to create, update, or delete calendar events without manual clicks
- When you want to check availability and find free slots before scheduling
- When you need to manage attendees by email addresses and adjust organizer behavior
- When you need to list calendars and discover IDs for integration
- When you want to search and browse events within a date range
Quick Start
- Step 1: Add the Rube MCP server https://rube.app/mcp in your client configuration and verify RUBE_SEARCH_TOOLS is available
- Step 2: Run RUBE_MANAGE_CONNECTIONS with toolkit googlecalendar and complete the OAuth flow if prompted
- Step 3: Ensure the connection status shows ACTIVE before running any workflows
Best Practices
- Verify the Rube MCP connection is ACTIVE before running workflows
- Always use ISO 8601 start_datetime and an IANA timezone
- Pass attendees as an array of email addresses, not names
- Run free-slot checks (find slots) before creating events to avoid conflicts
- Specify calendar_id precisely (e.g., 'primary' or a specific calendar ID) and note Meet link behavior and organizer inclusion
Example Use Cases
- Create a weekly team standup on the primary calendar with attendees and a location
- Find available time slots across calendars and schedule a client meeting
- Update an event's time, add/remove attendees, and change the location
- Delete an obsolete event and ensure attendees are notified accordingly
- List all calendars and extract their IDs for downstream apps
Frequently Asked Questions
Related Skills
ansible
chaterm/terminal-skills
Ansible 自动化运维
shell-scripting
chaterm/terminal-skills
Bash Shell 脚本编写
email-sequence
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
cron
chaterm/terminal-skills
定时任务管理
programmatic-seo
coreyhaines31/marketingskills
When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.
Playwright Browser Automation
jpulido240-svg/playwright-skill
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.