# Google Calendar AI integration on Definable

> Google Calendar is a time management tool providing scheduling features, event reminders, and integration with email and other apps for streamlined organization

## What this connects

Google Calendar is a time management tool providing scheduling features, event reminders, and integration with email and other apps for streamlined organization

Vendor: https://calendar.google.com

## Tools available

**44** tools available. First 12:

- `GOOGLECALENDAR_ACL_DELETE` — Delete ACL Rule — Deletes an access control rule from a Google Calendar. Use when you need to remove sharing permissions for a user, group, or domain.
- `GOOGLECALENDAR_ACL_GET` — Get ACL Rule — Retrieves a specific access control rule for a calendar. Use when you need to check permissions for a specific user, group, or domain.
- `GOOGLECALENDAR_ACL_INSERT` — Create ACL Rule — Creates an access control rule for a calendar. Use when you need to grant sharing permissions to a user, group, or domain.
- `GOOGLECALENDAR_ACL_LIST` — List ACL Rules — Retrieves the list of access control rules (ACLs) for a specified calendar, providing the necessary 'rule_id' values required for updating specific ACL rules.
- `GOOGLECALENDAR_ACL_PATCH` — Patch ACL Rule — Updates an existing access control rule for a calendar using patch semantics (partial update). This allows modifying specific fields without affecting other properties. IMPORTANT: The ACL rule must already exist on the calendar. This action cannot create new rules. If you receive a 404 Not Found error, the rule does not exist - use ACL insert to create it first, or use ACL list to verify available rules. Each patch request consumes three quota units. For domain-type ACL rules, if PATCH fails with 500 error, this action will automatically fallback to UPDATE method.
- `GOOGLECALENDAR_ACL_UPDATE` — Update ACL Rule — Updates an access control rule for the specified calendar.
- `GOOGLECALENDAR_ACL_WATCH` — Watch ACL Changes — Tool to watch for changes to ACL resources. Use when you need to set up real-time notifications for access control list modifications on a calendar.
- `GOOGLECALENDAR_BATCH_EVENTS` — Batch Events — Execute up to 1000 event mutations (create/patch/delete) in one Google Calendar HTTP batch request with per-item status/results. Use this to materially reduce round-trips for bulk operations like migrations, cleanup, or large-scale updates.
- `GOOGLECALENDAR_CALENDAR_LIST_DELETE` — Remove Calendar from List — Tool to remove a calendar from the user's calendar list. Use when you need to unsubscribe from or hide a calendar from the user's list.
- `GOOGLECALENDAR_CALENDAR_LIST_GET` — Get Single Calendar by ID — Retrieves metadata for a SINGLE specific calendar from the user's calendar list by its calendar ID. This action requires a calendarId parameter and returns details about that one calendar only. NOTE: This does NOT list all calendars. To list all calendars in the user's calendar list, use GOOGLECALENDAR_CALENDAR_LIST_LIST instead.
- `GOOGLECALENDAR_CALENDAR_LIST_INSERT` — Insert Calendar into List — Inserts an existing calendar into the user's calendar list, making it visible in the UI. Calendars (e.g., newly created ones) won't appear in the list or UI until explicitly inserted.
- `GOOGLECALENDAR_CALENDAR_LIST_PATCH` — Patch Calendar List Entry — Updates an existing calendar on the user's calendar list using patch semantics. This method allows partial updates, modifying only the specified fields.

## Auth

Auth schemes: `OAUTH2`. Managed by Definable: `OAUTH2` — no client credentials required from the user.

## How agents use Google Calendar

Inside a Definable workflow, Google Calendar is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Google Calendar** — the Researcher (GPT-5.5) pulls context from Google Calendar (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Google Calendar** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Google Calendar (create record, post message, draft email).
- **Designer / Engineer → Distributor → Google Calendar** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Google Calendar (attach file, open PR comment, post status).

The Verifier checks every Google Calendar call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- scheduling & booking — https://definable.ai/apps/category/scheduling-&-booking/

## Related

- HTML page: https://definable.ai/apps/googlecalendar/
- Same category (scheduling & booking): https://definable.ai/apps/category/scheduling-&-booking/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt