Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

next
md 59 lines 3.05 KB
Rendered Raw
1 ---
2 type: "reference"
3 title: "Google Calendar"
4 description: "Public support knowledge for Google Calendar."
5 category: "auth-config"
6 visibility: "public"
7 timestamp: "2026-06-24T00:00:00Z"
8 tags:
9 - "google_calendar"
10 ---
11 # Google Calendar
12
13 ## Create a Google Calendar integration to access tools and triggers
14
15 Create a Google Calendar integration/auth config, connect the account, and then use the Google Calendar toolkit's tools and triggers through that connected account.
16
17 ## Updating RSVP status has an attendee-list API limitation
18
19 Google Calendar can limit RSVP/status updates when an event has multiple attendees. Update the authenticated user's RSVP and then re-add the attendees, or resend the attendee list with the updated status.
20
21 ## Canceled/deleted event trigger sends payloads for canceled or deleted events
22
23 `GOOGLECALENDAR_EVENT_CANCELED_DELETED_TRIGGER` sends a payload when an event is canceled or deleted.
24
25 ## Multiple triggers for the same slug/user can target different calendar IDs
26
27 Multiple triggers for the same trigger slug and user are supported when each trigger is configured for a different `calendarId`.
28
29 ## `calendar.events` scope is required for event list/fetch flows
30
31 Ensure the connected account has `https://www.googleapis.com/auth/calendar.events` when calling event-list or event-fetch tools that require event access.
32
33 ## Google Calendar triggers now return full event data instead of only an ID
34
35 The newer Google Calendar new-event trigger payload includes complete event data rather than only the event ID.
36
37 ## Google Calendar trigger moved toward polling for more verbose payloads
38
39 Google Calendar trigger behavior moved from webhook-style delivery toward polling so payloads can include more detail and require less follow-up processing. Existing trigger flows were preserved while polling could be introduced separately where needed.
40
41 ## Use trigger-types endpoint to retrieve Google Calendar trigger info programmatically
42
43 Use the trigger-types endpoint to retrieve Google Calendar trigger metadata programmatically, and use the triggers documentation for setup guidance.
44
45 ## Use Find Free Slots when you need processed availability; free/busy does not do timezone processing
46
47 Use the find-free-slots tool when you need processed availability. Query-free/busy returns provider data without extra processing such as timezone handling, so callers using free/busy may need to process it themselves.
48
49 ## Use `primary` as calendar ID; `me` is not valid for calendar ID
50
51 For Google Calendar tools, use a calendar ID such as `primary`; `me` is not a valid Google Calendar ID.
52
53 ## Use latest Google Calendar toolkit version when filters are ignored
54
55 Older pinned Google Calendar toolkit versions can drop or remap filters such as `timeMin` and `timeMax` before the request reaches Google. Use the latest toolkit version or v3.1/latest behavior when filter changes produce identical results.
56
57 ## Google Calendar meeting link is returned in `hangout_link`
58
59 After creating or updating a calendar event with conferencing, read the generated meeting URL from the response's `hangout_link` field.