Skip to main content
The Google Calendar tool covers calendar lists, calendars, events, attendees, recurrence and free/busy queries. Its key is google-calendar. Coverage lists 20 routes, including quickAdd and import, which always return a coverage gap.

Connect

Node
This is what ancha connect google-calendar --lang ts prints. Pass rootUrl on each request, with a trailing /. A global rootUrl keeps only the origin and drops the path. Use primary for the owner’s calendar.

Endpoints

Unsupported features on listed routes return HTTP 400 in Google’s error shape. Unknown routes return HTTP 404. Both carry x-ancha-gap: 1. The client retries 5xx responses, so these errors use 4xx responses.

Starter data

The starter data belongs to Ben Carter, ben@acme.example, in America/Los_Angeles. The events include attendee responses and Google Meet links. Run ancha twins seed google-calendar --full to print every event, its date and its scene seed fields.

Checks

Google Calendar has no state checks. Use trace checks, for example { called: "POST /calendar/v3/calendars/*/events" } or { not_called: "DELETE /calendar/v3/calendars/*/events/*" }.

Limits

  • You can read recurring occurrences and change or cancel a whole series. Changing or deleting one occurrence is a gap.
  • An invitee can answer an invitation, but cannot edit its other fields.
  • quickAdd, import, ACLs, watch channels and sync tokens are gaps.
  • Attachments, working locations, attaching existing conferences and group expansion in free/busy queries are gaps.