> ## 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 Drive and Microsoft 365 to Scout Agents

> Give Scout agents access to Google Drive, SharePoint, OneDrive, and Microsoft 365 to read, summarize, and write files across your entire file ecosystem.

Your files already contain a significant amount of institutional knowledge — strategy decks, QBR materials, policy documents, project briefs. Connecting Google Drive or Microsoft 365 means your agents can read that content directly instead of relying on you to copy and paste it. You ask the agent to summarize a folder, find an outdated policy, or write an exec brief from a deck, and it does the work against your actual files.

## What Your Agent Can Do

| Capability            | Google Drive                       | Microsoft 365                          |
| --------------------- | ---------------------------------- | -------------------------------------- |
| **Read documents**    | Docs, Sheets, Slides               | Word, Excel, PowerPoint                |
| **List folders**      | Browse Drive folder structure      | Browse SharePoint sites and OneDrive   |
| **Search files**      | Find by name or keyword            | Find by name or keyword                |
| **Write files**       | Create and update Google Docs      | Create and update Word and Excel files |
| **Sync to Databases** | Pull content into Scout for search | Pull content into Scout for search     |

## Connecting Google Drive

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

  <Step title="Sign in and authorize">
    You'll be redirected to Google's authorization screen. Sign in and approve the permissions Scout requests:

    | Permission       | What it's for                              |
    | ---------------- | ------------------------------------------ |
    | `drive.readonly` | Read your files and folders                |
    | `drive.file`     | Create and edit files your agent generates |

    Scout only accesses folders your agent is explicitly configured to use — it won't browse your entire Drive without direction.
  </Step>

  <Step title="Verify the connection">
    Back in Scout, Google Drive should show as **Connected** in your integrations list.
  </Step>

  <Step title="Enable Drive tools on your agent">
    Open your agent, go to the **Tools** tab, and toggle on the Google Drive tools. Then add path conventions to your agent's **Instructions** (see the guardrail section below).
  </Step>
</Steps>

### What Your Agent Can Do with Google Drive

Once Google Drive is connected and enabled:

* **Read Docs, Sheets, and Slides** — pull content from any file you've shared access to
* **List folders** — navigate your Drive structure to find files by path
* **Search by keyword or filename** — locate documents without knowing the exact path
* **Summarize documents** — condense long files into structured briefs
* **Create and update files** — write outputs back to specific folders in Drive

## Connecting Microsoft 365

Microsoft 365 connects via OAuth through your Microsoft account, giving agents access to OneDrive, SharePoint, and the full Office file suite.

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

  <Step title="Sign in and authorize">
    You'll be redirected to Microsoft's authorization screen. Sign in with your Microsoft account and approve the permissions:

    | Permission        | What it's for                                   |
    | ----------------- | ----------------------------------------------- |
    | `Files.ReadWrite` | Read and write files in OneDrive and SharePoint |
    | `Sites.Read.All`  | Browse SharePoint sites and their contents      |
  </Step>

  <Step title="Verify the connection">
    Back in Scout, Microsoft 365 should show as **Connected** in your integrations list.
  </Step>

  <Step title="Enable M365 tools on your agent">
    Open your agent, go to the **Tools** tab, and toggle on the Microsoft 365 tools. Add path conventions to your agent's **Instructions** using the guardrail below.
  </Step>
</Steps>

### What Your Agent Can Do with Microsoft 365

Once Microsoft 365 is connected and enabled:

* **Read Word, Excel, and PowerPoint files** — pull content from OneDrive and SharePoint
* **Browse SharePoint sites** — navigate site libraries and document collections
* **Search across OneDrive** — find files by name or keyword
* **Create and update Word and Excel files** — write outputs back to your file system
* **Summarize spreadsheets** — extract key figures and tables from Excel workbooks

<Note>
  If you connect both Google Drive and Microsoft 365, you can enable both tool sets on the same agent. Agents can reference files across both ecosystems in a single workflow — useful for teams running mixed environments.
</Note>

## Instruction Guardrails

Without explicit path instructions, an agent writing files will choose its own output location, which makes files hard to find later. This instruction block establishes consistent read and write behavior:

```markdown theme={null}
For file operations:

1. List folders before reading or writing.
2. Use explicit folder paths for outputs (e.g., /reports/weekly/).
3. Keep source files and generated files in separate folders.
4. Return the final file path and name after each write.
```

Add this to your agent's **Instructions** before enabling any write tools.

<Tip>
  If your agent frequently creates files, add a naming convention to your instructions: "Name new files as `[YYYY-MM-DD] - [Topic]` and place them in the `/reports/` folder." This keeps your file system organized without manual cleanup.
</Tip>

## Testing Your Integration

<Steps>
  <Step title="Test folder listing">
    Ask your agent to list the files in a specific folder. It should return the contents with file names and types — no writes, no side effects.
  </Step>

  <Step title="Test document reading">
    Ask it to read a document and summarize it. Verify the summary is accurate and grounded in the actual file content.
  </Step>

  <Step title="Test file creation">
    If write access is enabled, ask the agent to create a test file with a specific name in a specific folder. Confirm it appears in Drive or OneDrive at the correct path.
  </Step>
</Steps>

## Prompt Examples

These prompts work once Google Drive or Microsoft 365 is connected and enabled on your agent:

* "Read the latest QBR deck in Google Drive and write an executive brief."
* "Find policy updates in Microsoft 365 and summarize changes by department."
* "Create a weekly summary doc from these folders and save it to /reports/weekly."
* "List everything in the /contracts folder and flag any files older than 90 days."
* "Summarize all the Excel reports in the /finance/Q2 folder and identify key trends."
* "Find any Google Slides decks about product roadmap and extract the key initiatives."

## Use Cases

**Research and synthesis** — Ask your agent to read five documents in a folder and produce a structured summary with themes, conflicts, and open questions. The agent does the reading; you focus on the decisions.

**Meeting prep** — Before a QBR or board meeting, ask your agent to pull the relevant decks and reports from Drive, summarize the key numbers and narratives, and write a structured pre-read brief. Combine this with calendar context for a complete prep package.

**Executive briefs** — Regularly ask your agent to distill a folder of reports into a one-page brief for leadership. Point it at /reports/weekly in Drive, set a naming convention, and let it run on a schedule.

**Document hygiene** — Ask your agent to list files in a folder, identify anything older than a specified threshold, and flag items for review or archival. Useful for keeping shared drives from accumulating outdated materials.

## Troubleshooting

<details>
  <summary>Agent can't find a file I know exists</summary>

  Check two things:

  * The folder path in your instructions matches exactly — capitalization matters in both Drive and SharePoint paths
  * The file is in a location Scout has access to — personal folders outside a shared drive may not be accessible depending on your permissions setup
</details>

<details>
  <summary>Agent created a file but I can't find it</summary>

  Ask your agent: "What path did you save the file to?" and check that location. If it's missing, the agent may have written to a default working folder rather than your intended destination. Add an explicit output path to your agent's instructions to prevent this.
</details>

<details>
  <summary>I connected the integration but my agent doesn't see any tools</summary>

  1. Go to your agent's **Settings** and open the **Tools** section
  2. Make sure the Drive or Microsoft 365 tools are toggled **on**
  3. Confirm the integration shows as **Connected** at [studio.scoutos.com/integrations](https://studio.scoutos.com/integrations)

  If it still doesn't work, try disconnecting and reconnecting the integration.
</details>

## Next Steps

<CardGroup cols={2}>
  <Card title="CRM" icon="database" href="/integrations/crm">
    Combine file content with CRM data for meeting prep and account research.
  </Card>

  <Card title="Email & Calendar" icon="envelope" href="/integrations/email-calendar">
    Pull document context into email drafts and pre-call briefs.
  </Card>

  <Card title="Slack" icon="slack" href="/integrations/slack">
    Post document summaries and file-based digests to team channels.
  </Card>

  <Card title="Integrations Overview" icon="grid" href="/integrations/overview">
    See the full integration stack and recommended connection order.
  </Card>
</CardGroup>