> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/solutions-engineer/getting-started/calendar-auto-join.md).

# Calendar auto-join

Connect your calendar so Samantha joins your Zoom and Google Meet meetings on her own, with rules for which meetings she joins and a switch per meeting.

The [**Calendar**](https://app.spara.co/meeting-agents/calendar) tab sends Samantha to your meetings on its own, with no dispatch form to fill in. Connect your calendar once, choose which kinds of meetings she joins, and she turns up a minute early.

{% hint style="info" %}
The screenshot below uses a sample calendar.
{% endhint %}

<figure><img src="https://821105055-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTMt4EjieWT1FfljMBJHI%2Fuploads%2Fgit-blob-fee10819131f5a69d948228bbf0c5588c86d4aed%2FMeeting%20Agents%20Calendar.png?alt=media" alt=""><figcaption><p>The Calendar tab with a connected Google calendar</p></figcaption></figure>

1. **Connected calendar**: Auto-join reads the calendar of the inbox you connected for Scout, Google or Outlook. If it isn't connected, or is missing calendar access, **Go to Scout** takes you there to fix it (see [Scout: Connect your tools](https://docs.spara.com/scout/getting-started/connect-your-tools)). **Disconnect** stops auto-join only; your inbox stays connected.
2. **Live Assistant**: The agent that joins your meetings: Samantha, or another of your Live Assistant agents. **None (auto-join off)** turns auto-join off.
3. **Product demo (optional)**: One product demo agent to go with her, for its visuals and demo topics.
4. **Which meetings she joins**: **Internal** (everyone invited is on your company's email domains), **External** (someone invited isn't), **Organized by someone else**, and **Declined or pending**.
5. **Upcoming meetings**: Your next 7 days. Each meeting says what will happen, for example "Your Live Assistant joins a minute early", or why it's skipped. Turn a meeting off to skip it, or on to send her anyway.
6. **Series**: On a recurring meeting, skip or join every meeting in the series, or go back to your preferences for it.

A few things to know:

* Auto-join covers Zoom and Google Meet. Send Teams meetings from **Dispatch**; see [Send Samantha to a meeting](/solutions-engineer/getting-started/send-samantha-to-a-meeting.md).
* It skips meetings with no single Zoom or Google Meet link, with no one else invited, longer than 3 hours, or already underway. It also stops at 5 meetings a day per rep and 20 per account. The meeting's row says why it skipped one.
* If a teammate's Samantha is already going to a meeting, or you sent an agent to its link from **Dispatch**, the row names that agent and auto-join doesn't send a second one.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spara.com/solutions-engineer/getting-started/calendar-auto-join.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
