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

# Connect Google Calendar to Your Scout Agents

> Give Scout agents access to Google Calendar to check schedules, find open slots, book meetings, and automate scheduling workflows.

Finding meeting times, prepping for calls, and keeping a calendar accurate is steady, low-value work that adds up fast. Connecting Google Calendar lets your agents read your schedule, propose availability across timezones, and book meetings on your behalf — grounded in your real calendar data rather than guesswork.

## Connecting Google Calendar

Google Calendar connects through Google OAuth. If you've already connected [Gmail](/integrations/gmail), you can add Calendar access without authorizing from scratch — both services use the same Google account.

<Steps>
  <Step title="Open the Integrations page">
    Go to [studio.scoutos.com/integrations](https://studio.scoutos.com/integrations) and click **Connect** next to **Google Calendar**.
  </Step>

  <Step title="Authorize Calendar access">
    Review the permissions and click **Allow**. Scout requests:

    | Scope               | What it's for                     |
    | ------------------- | --------------------------------- |
    | `calendar.readonly` | Read your events and availability |
    | `calendar.events`   | Create and update events          |
  </Step>

  <Step title="Enable tools on your agent">
    Open your agent's **Tools** tab and toggle on the Google Calendar tools.
  </Step>

  <Step title="Add the scheduling guardrail">
    In your agent's **Instructions**, add the guardrail snippet from the section below so the agent confirms details before booking.
  </Step>
</Steps>

## What Your Agent Can Do with Google Calendar

Once Google Calendar is connected and enabled on your agent:

* **Check your schedule** — read upcoming events, participants, and descriptions
* **Find open slots** — identify available windows across a time range or set of participants
* **Create events** — book meetings with titles, descriptions, participants, and video links
* **Propose availability** — suggest times across timezones based on real calendar data
* **Generate pre-meeting context** — combine calendar events with email history and CRM records for a full prep brief

<Warning>
  A booked meeting shows up on someone else's calendar immediately. Use the guardrail below so the agent confirms the timezone, participants, and time before creating any event.
</Warning>

## Instruction Guardrails

Calendar actions reach real people immediately. This instruction block enforces a confirm-before-book pattern:

```markdown theme={null}
For calendar actions:

1. Confirm timezone, participants, and time before booking.
2. Include a concise rationale for each scheduling decision.
3. Show me the invite details before creating the event.
4. Return event IDs after actions complete.
```

<Tip>
  If your agent uses the wrong timezone, specify it in the agent's **Instructions** or in each prompt: "Always use Pacific Time (PT) for scheduling unless I specify otherwise."
</Tip>

## Prompt Examples

These prompts work once Google Calendar is connected and enabled on your agent:

* "Find two 30-minute windows next week for a call with this group. Use Pacific time."
* "Book a 45-minute kickoff call with these four attendees sometime next week."
* "List my events for the next three days and flag any conflicts."
* "Create a prep brief for tomorrow's customer call using my calendar and the last 30 days of email context."
* "Propose three times that work across US Eastern and Central European time."

## Testing Your Integration

Run through these steps in order before using the agent in production:

<Steps>
  <Step title="Test calendar read">
    Ask it to list your events for the next three days. Verify that it reads your calendar correctly and uses the right timezone.
  </Step>

  <Step title="Test finding availability">
    Ask it to find open windows next week. Confirm the slots it returns don't conflict with existing events.
  </Step>

  <Step title="Test a booking action">
    Only after the read steps work, test a booking action — start with an event on your own calendar before involving others.
  </Step>
</Steps>

## Troubleshooting

<details>
  <summary>Agent can't read my calendar</summary>

  Check that:

  * The integration shows as **Connected** in [studio.scoutos.com/integrations](https://studio.scoutos.com/integrations)
  * Calendar tools are toggled **on** in your agent's **Tools** tab
  * You authorized all requested permissions during setup — partial authorization can cause read failures

  Try disconnecting and reconnecting the integration if you're still getting errors.
</details>

<details>
  <summary>Agent is using the wrong timezone for scheduling</summary>

  Specify your timezone in your agent's instructions or in each prompt:

  ```
  Always use Pacific Time (PT) for scheduling unless I specify otherwise.
  ```
</details>

## Use Cases

**Scheduling across teams** — Ask your agent to find two 45-minute windows next week that work for four people across two timezones and propose them as calendar invites. The agent reads real availability and avoids conflicts.

**Pre-meeting prep** — Before a call, ask your agent to pull the relevant event, combine it with email history and CRM records, and generate a structured prep brief with context and talking points.

**Calendar hygiene** — Ask your agent to review the week ahead, flag double-bookings or back-to-back conflicts, and suggest fixes before they become a problem.

## Next Steps

<CardGroup cols={2}>
  <Card title="Gmail" icon="envelope" href="/integrations/gmail">
    Add email so agents can draft follow-ups and combine inbox context with your schedule.
  </Card>

  <Card title="Salesforce & HubSpot" icon="database" href="/integrations/salesforce">
    Add Salesforce or HubSpot context to pre-meeting briefs.
  </Card>

  <Card title="Slack" icon="slack" href="/integrations/slack">
    Route calendar digests to team channels automatically.
  </Card>

  <Card title="Google Drive" icon="google-drive" href="/integrations/google-drive">
    Pull document context into meeting prep workflows.
  </Card>
</CardGroup>