GWS Calendar Rapid

Execute Google Workspace Calendar operations for event management, scheduling, and availability queries.

When to Use This Command

Run this command when you need to:

• Create, update, or delete calendar events programmatically across your Workspace domain
• Query free/busy availability for meeting scheduling across multiple attendees
• Manage calendar sharing permissions and access control lists in bulk

Consider alternatives when:

• You need to set up recurring event patterns with complex RRULE specifications through the Calendar UI
• You want to browse calendars visually and the web interface provides better spatial context

Quick Start

Configuration

Copy
name: gws-calendar-rapid
type: command
category: google-workspace

Example Invocation

Copy
claude command:run gws-calendar-rapid --action freebusy --attendees "[email protected],[email protected]" --duration 60

Example Output

Checking availability...
  Attendees: [email protected], [email protected]
  Duration: 60 minutes
  Search window: next 5 business days

Available slots:
  Mon Mar 16  10:00 - 11:00  Both available
  Mon Mar 16  14:00 - 15:00  Both available
  Tue Mar 17  09:00 - 10:00  Both available
  Wed Mar 18  11:00 - 12:00  Both available
  Thu Mar 19  15:00 - 16:00  Both available

5 slots found. Use --book to create an event in the first available slot.

Core Concepts

Calendar Operations Overview

Aspect	Details
Events	Create, read, update, delete events with attendees and conferencing
Free/Busy	Query availability across multiple calendars for scheduling
ACLs	Manage calendar sharing: owner, writer, reader, freeBusyReader
Calendars	List, create, and manage calendar resources and room bookings
Notifications	Configure event reminders via email or push notifications

Scheduling Workflow

Query Attendee List
        |
        v
Fetch Free/Busy Data
  (for each attendee)
        |
        v
Find Overlapping Availability
        |
        v
Rank Slots by Preference
  (time-of-day, gap between meetings)
        |
        v
Present Options or Auto-Book
        |
        v
Send Invitations

Configuration

Parameter	Type	Default	Description
action	string	(required)	Operation: create, update, delete, list, freebusy
attendees	string	(none)	Comma-separated email addresses for event or freebusy
duration	integer	30	Event duration in minutes
calendar	string	primary	Target calendar ID or alias
window	integer	5	Number of business days to search for availability

Best Practices

1. Check availability before creating events - Use the freebusy action to find open slots rather than creating events that conflict with existing meetings and generate decline responses.

2. Include timezone in event creation - Always specify the timezone explicitly when creating events for distributed teams. Relying on server defaults causes confusion across time zones.

3. Use calendar resources for rooms - Instead of mentioning room names in event descriptions, book calendar resources so room availability is tracked automatically by Workspace.

4. Set appropriate reminders - Configure reminders based on event importance. Default reminders may not suit all meeting types and excessive notifications reduce their effectiveness.

Common Issues

1. Free/busy returns empty for external attendees - External users may not share free/busy data with your domain. Contact them directly or use a scheduling link service instead.

2. Event creation fails with 403 - Verify you have write access to the target calendar. Shared calendars may only grant read access, requiring the owner to update your ACL permissions.

3. Recurring event updates affect all instances - When updating a recurring event, specify whether to change just this instance or all future instances using the instance-mode parameter. Modifying a single occurrence creates an exception event while modifying all instances changes the series definition.

4. Calendar API quota exhausted - High-frequency operations like syncing hundreds of events can exhaust your daily API quota. Batch related operations together and implement exponential backoff on rate limit responses to stay within Google's quota boundaries.