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

# Google Calendar

> Let your apps book appointments, check availability, and create events with Google Meet links—using your organization's calendar or each user's own.

Google Calendar lets your apps work with real calendars—create and update events, check when people are free or busy, and attach Google Meet links. You connect it in your dashboard, then describe what you want and the agent builds it.

## Two ways to use it

The first thing to decide is **whose calendar** your app works with.

|                    | Your organization's calendar                                                                              | Your users' own calendars                                                                       |
| ------------------ | --------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| **Whose calendar** | One Google account you connect                                                                            | Each end user connects their own                                                                |
| **Setup**          | Connect & grant in [Settings → Integrations](https://www.stardeck.ai/dashboard/settings?tab=integrations) | None—the agent builds it into your app                                                          |
| **Good for**       | A shared business calendar, staff scheduling, a single bookable resource                                  | Personal scheduling, syncing events to each user's calendar                                     |
| **Guide**          | [Connect your calendar](/connected-services/google-calendar/connecting)                                   | [Let users connect their own calendars](/connected-services/google-calendar/end-user-calendars) |

You can use both in the same app—for example, book a slot on *your* business calendar while also dropping the event onto the *customer's* calendar.

```mermaid theme={null}
flowchart LR
    App["📱 Your app"] -- "signed request" --> SD["☁️ Stardeck"]
    SD -- "holds Google credentials" --> GC["📅 Google Calendar"]
    GC -- "events, free/busy" --> SD
    SD -- "response" --> App
```

Your app never holds Google tokens—Stardeck brokers every call. See [Connected Services](/connected-services/overview) for the shared security model.

## What you can build

Describe what you want in plain English in the project chat. Some examples:

**Book appointments**

```
When a customer picks a time slot, create an event on my Google Calendar and invite them
```

**Add a video call automatically**

```
Every booking should include a Google Meet link in the calendar invite
```

**Check availability before confirming**

```
Before showing open slots, check my calendar for free/busy times so I'm never double-booked
```

**Keep customers in the loop**

```
When an appointment is rescheduled, update the calendar event and email everyone the new time
```

You describe the outcome—the agent designs the flow and wires it up.

## Availability & cost

Connecting Google Calendar carries no extra Stardeck fee. Usage is subject to Google's own Calendar API quotas, which are generous for typical app traffic.

## Next steps

<CardGroup cols={2}>
  <Card title="Connect your calendar" icon="plug" href="/connected-services/google-calendar/connecting">
    Link your organization's Google account and grant it to your apps
  </Card>

  <Card title="Users' own calendars" icon="users" href="/connected-services/google-calendar/end-user-calendars">
    Let your app's end users connect their personal Google Calendars
  </Card>

  <Card title="Connected Services" icon="link" href="/connected-services/overview">
    How linked accounts work across the platform
  </Card>

  <Card title="Email" icon="envelope" href="/email">
    Pair calendar events with confirmation emails
  </Card>
</CardGroup>
