> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/integrations/call-recording/google-meet.md).

# Google Meet

Connect Pylon to Google Meet to ingest call recordings.

### Setup

Click into the App Directory from your Pylon dashboard and then click on the Google Meet integration to view setup instructions. Make sure you are a Google Workspace administrator before going through the app install process. See the [Google Meet setup guide](https://support.usepylon.com/articles/7015897513-how-do-i-integrate-google-meet-gemini-with-pylon?lang=en).

### Usage

Historical Google Meet calls (within previous 30 days) automatically backfill into Pylon, and new calls will automatically get ingested and associated with the correct account.

Google Meet calls will also be used as data context for Pylon features like [Ask AI](https://docs.usepylon.com/pylon-docs/platform/ask-ai), [Account Copilot](https://docs.usepylon.com/pylon-docs/account-intelligence/accounts/copilot), and [Account Widgets](/pylon-docs/account-intelligence/notebooks/blocks.md), and will appear on the activity timeline for accounts and related issues.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FvE07elxhz5H35z7st7Ng%2FGoogle%20meet%20integration.png?alt=media&amp;token=7dc6d54b-ab3c-41c2-a65e-9d4b15672df9" alt=""><figcaption></figcaption></figure>


---

# 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.usepylon.com/pylon-docs/integrations/call-recording/google-meet.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.