Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | Use this guide to connect Google Calendar, work with event data and availability, configure triggers, and troubleshoot version-specific behavior. |
| 2 | |
| 3 | ## Connect a Google Calendar account |
| 4 | |
| 5 | 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. |
| 6 | |
| 7 | Ensure the connected account has `https://www.googleapis.com/auth/calendar.events` when calling event-list or event-fetch tools that require event access. |
| 8 | |
| 9 | ## Work with events and availability |
| 10 | |
| 11 | **Update RSVP status with the attendee-list limitation in mind.** 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. |
| 12 | |
| 13 | **Use Find Free Slots for 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. |
| 14 | |
| 15 | **Use `primary` as the calendar ID.** For Google Calendar tools, use a calendar ID such as `primary`; `me` is not a valid Google Calendar ID. |
| 16 | |
| 17 | **Read generated meeting links from `hangout_link`.** After creating or updating a calendar event with conferencing, read the generated meeting URL from the response's `hangout_link` field. |
| 18 | |
| 19 | ## Configure Google Calendar triggers |
| 20 | |
| 21 | **Handle canceled or deleted events.** `GOOGLECALENDAR_EVENT_CANCELED_DELETED_TRIGGER` sends a payload when an event is canceled or deleted. |
| 22 | |
| 23 | **Create separate trigger instances for separate calendars.** Multiple triggers for the same trigger slug and user are supported when each trigger is configured for a different `calendarId`. |
| 24 | |
| 25 | **Expect full event data from newer triggers.** The newer Google Calendar new-event trigger payload includes complete event data rather than only the event ID. 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. |
| 26 | |
| 27 | **Retrieve trigger metadata programmatically.** Use the trigger-types endpoint to retrieve Google Calendar trigger metadata programmatically, and use the triggers documentation for setup guidance. |
| 28 | |
| 29 | ## Troubleshoot ignored event filters |
| 30 | |
| 31 | 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. |