Google Calendar#

Access Google Calendar via the Google Calendar API with OAuth authentication. Check calendars, find free time, schedule meetings, and update events.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure Google Calendar API access yourself.

Setup in 3 Steps#

Step 1: InstallStep 2: Pair AccountStep 3: Connect Google Calendar_App-specific connection GIF coming soon_Run the install command in OpenClawSign in and approve the deviceOpen the dashboard and connect Google Calendar

How It Works#

text

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│ Google Calendar  │
│   (User Chat)   │     │   (OAuth)    │     │   API (REST)     │
└─────────────────┘     └──────────────┘     └──────────────────┘
         │                       │                       │
         │  1. Install Plugin    │                       │
         │  2. Pair Device       │                       │
         │  3. Connect Google Calendar                    │
         │                       │  4. Secure Token      │
         │                       │  5. Proxy Requests    │
         │                       │                       │
         ▼                       ▼                       ▼
   ┌──────────┐           ┌──────────┐           ┌──────────┐
   │  SKILL   │           │ Dashboard│           │ Calendar │
   │  File    │           │ Auth     │           │ Events   │
   └──────────┘           └──────────┘           └──────────┘

Install#

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

bash

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for Google Calendar again."

Quick Start#

bash

# List calendars
clawlink_call_tool --tool "googlecalendar_list_calendars" --params '{}'

# Get current date/time for timezone-aware scheduling
clawlink_call_tool --tool "googlecalendar_get_current_date_time" --params '{"timezone": "America/New_York"}'

# List events for a specific day
clawlink_call_tool --tool "googlecalendar_events_list" --params '{"calendar_id": "primary", "time_min": "2025-01-15T00:00:00Z", "time_max": "2025-01-16T00:00:00Z"}'

# Find free time slots
clawlink_call_tool --tool "googlecalendar_find_free_slots" --params '{"time_min": "2025-01-15T09:00:00Z", "time_max": "2025-01-15T18:00:00Z", "calendar_ids": ["primary"], "meeting_duration_minutes": 60}'

Authentication#

All Google Calendar tool calls are authenticated automatically by ClawLink using the user's connected Google account.

No API key is required in chat. ClawLink stores the OAuth token securely and injects it into every Google Calendar API request on the user's behalf.

Getting Connected#

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with clawlink_begin_pairing if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=google-calendar and connect Google Calendar.
4. Call clawlink_list_integrations to verify the connection is active.

Connection Management#

List Connections#

bash

clawlink_list_integrations

Response: Returns all connected integrations. Look for google-calendar in the list.

Verify Connection#

bash

clawlink_list_tools --integration google-calendar

Response: Returns the live tool catalog for Google Calendar.

Reconnect#

If Google Calendar tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=google-calendar
2. After they confirm, call clawlink_list_integrations to verify
3. Then call clawlink_list_tools --integration google-calendar

Security & Permissions#

• Access is scoped to calendars accessible to the connected Google account.
• All write operations require explicit user confirmation. Before executing any event create, update, move, or delete, confirm the intended effect with the user.
• Destructive actions (deleting events, clearing calendars) are marked as high-impact and must be confirmed.
• Moves and deletions of events with attendees affect other people's calendars — treat these as especially sensitive.

Tool Reference#

Calendars#

ToolDescriptionModegooglecalendar_list_calendarsList all calendars in the user's calendar listReadgooglecalendar_get_calendarGet a specific calendar's metadataReadgooglecalendar_duplicate_calendarCreate a new empty calendarWritegooglecalendar_patch_calendarUpdate calendar title, description, timezoneWritegooglecalendar_calendars_deleteDelete a secondary calendarWritegooglecalendar_clear_calendarDelete all events from a calendarWrite

Events#

ToolDescriptionModegooglecalendar_events_listList events on a calendar with time filteringReadgooglecalendar_events_list_all_calendarsList events across all calendarsReadgooglecalendar_events_getGet a specific event by IDReadgooglecalendar_find_eventSearch events by text query and time rangeReadgooglecalendar_create_eventCreate a new calendar eventWritegooglecalendar_update_eventFull update of an existing eventWritegooglecalendar_patch_eventPartial update of event fieldsWritegooglecalendar_delete_eventDelete an event by IDWritegooglecalendar_events_moveMove an event to another calendarWritegooglecalendar_events_instancesGet instances of a recurring eventRead

Scheduling#

ToolDescriptionModegooglecalendar_find_free_slotsFind free/busy time slots across calendarsReadgooglecalendar_get_current_date_timeGet current date and time in a timezoneReadgooglecalendar_quick_addParse natural language to create a simple eventWrite

Attendees#

ToolDescriptionModegooglecalendar_remove_attendeeRemove an attendee from an eventWrite

Availability#

ToolDescriptionModegooglecalendar_freebusy_queryGet free/busy info for a list of calendarsRead

Access Control#

ToolDescriptionModegooglecalendar_acl_listList access control rules for a calendarReadgooglecalendar_acl_insertCreate an ACL rule (share calendar)Writegooglecalendar_acl_deleteDelete an ACL ruleWrite

Code Examples#

List today's events#

bash

clawlink_call_tool --tool "googlecalendar_events_list" \
  --params '{
    "calendar_id": "primary",
    "time_min": "2025-01-15T00:00:00-05:00",
    "time_max": "2025-01-15T23:59:59-05:00",
    "single_events": true,
    "order_by": "startTime"
  }'

Find free time for a meeting#

bash

clawlink_call_tool --tool "googlecalendar_find_free_slots" \
  --params '{
    "time_min": "2025-01-15T09:00:00-05:00",
    "time_max": "2025-01-15T17:00:00-05:00",
    "calendar_ids": ["primary"],
    "meeting_duration_minutes": 60
  }'

Create a meeting event#

bash

clawlink_call_tool --tool "googlecalendar_create_event" \
  --params '{
    "calendar_id": "primary",
    "summary": "Team Sync",
    "description": "Weekly team synchronization meeting",
    "start_datetime": "2025-01-15T10:00:00",
    "event_duration_minutes": 60,
    "timezone": "America/New_York",
    "attendees": ["colleague@example.com"]
  }'

Update an event#

bash

clawlink_call_tool --tool "googlecalendar_patch_event" \
  --params '{
    "calendar_id": "primary",
    "event_id": "abc123xyz",
    "summary": "Updated Team Sync",
    "start_datetime": "2025-01-15T11:00:00",
    "event_duration_minutes": 90
  }'

Discovery Workflow#

1. Call clawlink_list_integrations to confirm Google Calendar is connected.
2. Call clawlink_list_tools --integration google-calendar to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration google-calendar.
5. If no Google Calendar tools appear, direct the user to https://claw-link.dev/dashboard?add=google-calendar.

Execution Workflow#

text

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  list → get → find → search → describe → call               │
│                                                             │
│  Example: List calendars → Find free slots → Show options   │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                    │
│  list → get → describe → preview → confirm → call           │
│                                                             │
│  Example: Preview event creation → User confirms            │
│           → Execute create                                   │
└─────────────────────────────────────────────────────────────┘

1. For unfamiliar tools, ambiguous requests, or any write action, call clawlink_describe_tool first.
2. Use the returned guidance, schema, whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
3. Prefer read, list, search, and availability operations before writes.
4. For event changes or other high-impact actions, call clawlink_preview_tool first, then confirm with the user.
5. Execute with clawlink_call_tool. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

Notes#

• Timezone-aware scheduling: Always use IANA timezone identifiers (e.g., America/New_York, Europe/London) not abbreviations.
• UTC timestamps ending in Z are interpreted in UTC regardless of calendar timezone — use timezone-offset timestamps for local date queries.
• Primary calendar is referenced as calendar_id: "primary".
• Events with attendees automatically send invitations via Google Calendar.
• Deleting or moving events with attendees affects their calendars too — always confirm.
• No conflict checking is performed before event creation — use find_free_slots to detect overlaps.

Error Handling#

Status / ErrorMeaningTool not foundThe tool name does not exist in the current catalog. Verify with clawlink_list_tools --integration google-calendar.Missing connectionGoogle Calendar is not connected. Direct the user to https://claw-link.dev/dashboard?add=google-calendar.404 Not FoundCalendar or event does not exist. Verify the calendar_id and event_id.403 ForbiddenInsufficient permissions to access or modify the calendar.400 Bad RequestInvalid datetime format or timezone. Use ISO 8601 with timezone offset.Write rejectedUser did not confirm a write action. Always confirm before executing event creates, updates, moves, or deletes.

Troubleshooting: Tools Not Visible#

1. Check that the ClawLink plugin is installed: bash

   openclaw plugins list
   
   

2. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.

3. If a fresh chat does not help, run: bash

   openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
   openclaw gateway restart
   
   

4. After restart, tell the user to send /new again and retry.

Troubleshooting: Invalid Tool Call#

1. Ensure the integration slug is exactly google-calendar.
2. Use clawlink_describe_tool to verify parameter names and types before calling.
3. For write operations, always call clawlink_preview_tool first.

Resources#

• Google Calendar API Overview
• Google Calendar API Reference
• Event Resource
• ClawLink
• ClawLink Docs
• ClawLink Verification

Related Skills#

• Gmail — For email management alongside scheduling
• Google Meet — For video conferencing

---

Powered by ClawLink — an integration hub for OpenClaw