> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Let AI Agents Schedule Meetings in Google Calendar

> Let agents check availability, create events, and manage RSVPs in Google Calendar. Connect in one click, and the gateway keeps OAuth tokens hidden.

> [!WARNING]
>
> **Per-app Google setup is deprecated.** All Google apps now share one Google OAuth client and one Redirect URI. To use your own client, follow the [Google setup guide](/docs/integrations/google.md). Credentials saved for one Google app apply to all of them.

## Overview

Buckle connects AI agents to Google Calendar through Google's OAuth flow. Agents can list upcoming events, create new meetings, check availability, and manage RSVPs. The gateway injects OAuth credentials into requests to the Google Calendar API automatically.

This is useful for scheduling agents, meeting coordinators, or any agent that needs awareness of your calendar.

## What you will set up

* A Google Calendar connection through Google OAuth, in one click on Buckle Cloud or with your own client
* Automatic token injection on Calendar API requests
* Per-agent, per-tool access, such as approval before creating events

## Connect on Buckle Cloud (one click)

**1. Open the app**

Open the Buckle dashboard and navigate to **Settings** > **Apps** > **Google Calendar**.

**2. Authorize**

Click **Connect Google Calendar**. You'll go straight to Google: pick your account, review the permissions, and click **Allow**. No Google Cloud setup needed.

On self-hosted Buckle, or to use your own Google client on Cloud, see [Use your own Google client](#self-hosted).

## Use your own Google client

> [!NOTE]
>
> This is for self-hosted Buckle, and for Buckle Cloud when you choose **Custom credentials** instead of one-click. One Google client serves every Google app in Buckle, so you set it up once. If you already did it for another Google app, skip to step 2.

> [accordion] 1. Set up your Google client
>
> Follow the [Google setup guide](/docs/integrations/google.md). It enables the Google APIs, sets up the consent screen, creates the OAuth client, and adds the Redirect URI.
>
> You paste the client into **Settings** > **Apps** > **Google Calendar** > **Custom credentials**, under the Redirect URI the guide asks you to register:
>
> ![Buckle Custom credentials card for Google Calendar with the setup guide link, the Redirect URI and its copy button, and the Client ID and Client Secret fields.](https://mintcdn.com/onecli-17d3f772/hJP3XqgFsBDnXHKy/images/integrations/google-calendar/buckle-custom-credentials-google-calendar.png?fit=max\&auto=format\&n=hJP3XqgFsBDnXHKy\&q=85\&s=131b0c58684eefc95d766479e0a83ada)
>
> Custom credentials for Google Calendar in Buckle.

> [accordion] 2. Connect Google Calendar
>
> Open **Settings** > **Apps** > **Google Calendar**, select **Connect Google Calendar**, pick your Google account, and click **Allow**.
>
> ![Buckle connect window for Google Calendar showing Configuration required and the Configure credentials button.](https://mintcdn.com/onecli-17d3f772/hJP3XqgFsBDnXHKy/images/integrations/google-calendar/buckle-connect-google-calendar.png?fit=max\&auto=format\&n=hJP3XqgFsBDnXHKy\&q=85\&s=2aefebe03093bb98c3d5b2ee942b1304)
>
> The Google Calendar connect window before a Google client is set up.

## What agents can do

* List events on any of your calendars within a date range
* Get details for a specific event (attendees, location, video link, description)
* Create new events with attendees, location, and conferencing
* Update existing events (reschedule, change attendees, modify description)
* Delete or cancel events
* Check free/busy availability for one or more people
* Respond to event invitations (accept, decline, tentative)
* List all calendars on the account
* Create and manage secondary calendars

## Controlling access

Access is per agent: [grant](/docs/guides/agent-access.md) the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization [rules](/docs/guides/rules.md) add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches Google Calendar.

## FAQ

> [accordion] Can an agent check availability without creating events?
>
> Yes. When you [grant](/docs/guides/agent-access.md) the connection, allow read tools and block or require approval for writes.

> [accordion] Does the agent see my Google token?
>
> No. The token stays in Buckle, and the gateway adds it at the proxy. See [How it works](/docs/how-it-works.md).

> [accordion] How do I reconnect or switch accounts?
>
> Open **Settings** > **Apps** > **Google Calendar** and connect again with the account you want. Agents with access use the new connection automatically.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.