Skip to main content
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

CapabilityGoogle DriveMicrosoft 365
Read documentsDocs, Sheets, SlidesWord, Excel, PowerPoint
List foldersBrowse Drive folder structureBrowse SharePoint sites and OneDrive
Search filesFind by name or keywordFind by name or keyword
Write filesCreate and update Google DocsCreate and update Word and Excel files
Sync to DatabasesPull content into Scout for searchPull content into Scout for search

​
Connecting Google Drive

1

Open the Integrations page

Go to studio.scoutos.com/integrations and click Connect next to Google Drive.
2

Sign in and authorize

You’ll be redirected to Google’s authorization screen. Sign in and approve the permissions Scout requests:
PermissionWhat it’s for
drive.readonlyRead your files and folders
drive.fileCreate 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.
3

Verify the connection

Back in Scout, Google Drive should show as Connected in your integrations list.
4

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).

​
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.
1

Open the Integrations page

Go to studio.scoutos.com/integrations and click Connect next to Microsoft 365.
2

Sign in and authorize

You’ll be redirected to Microsoft’s authorization screen. Sign in with your Microsoft account and approve the permissions:
PermissionWhat it’s for
Files.ReadWriteRead and write files in OneDrive and SharePoint
Sites.Read.AllBrowse SharePoint sites and their contents
3

Verify the connection

Back in Scout, Microsoft 365 should show as Connected in your integrations list.
4

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.

​
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
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.

​
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: 
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.
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.

​
Testing Your Integration

1

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.
2

Test document reading

Ask it to read a document and summarize it. Verify the summary is accurate and grounded in the actual file content.
3

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.

​
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

​
Next Steps

CRM

Combine file content with CRM data for meeting prep and account research.

Email & Calendar

Pull document context into email drafts and pre-call briefs.

Slack

Post document summaries and file-based digests to team channels.

Integrations Overview

See the full integration stack and recommended connection order.