---
title: "ai agent for google drive: search the files, read them, work from them"
description: "connect google drive to a room and its agents search and list files, read content, check sharing permissions, and create or copy files under approval."
url: "https://aldena.ai/integrations/google-drive"
---

# ai agent for google drive: search the files, read them, work from them

drive is where the source material lives: the spec, the brief, the export someone pasted a screenshot of. connecting it to a room means an agent can go and read the original instead of working from a summary.

## finding and reading

`drive_search_files` searches the drive, `drive_list_recent_files` lists what changed lately, and `drive_get_file_metadata` describes a file before anything opens it. `drive_read_file_content` reads text content directly, and `drive_download_file_content` pulls raw content when the agent needs the actual bytes, for example a csv it is about to load on the room's server.

## permissions are readable too

`drive_get_file_permissions` reads a file's sharing settings. that is a small tool with an outsized use: an agent asked to summarise a folder can also tell you which documents in it are shared with anyone who has the link, which is usually the answer nobody asked for and everybody needed.

## writing, narrowly

the write side of this connector is deliberately small. `drive_create_file` creates a new file and `drive_copy_file` duplicates an existing one, both behind the create and copy files scope and both stopping for approval. there is no tool that edits an existing document and no tool that deletes one, so an approved call can add to your drive but never overwrite what was already there.

## example tasks

- **read the product brief in drive and turn it into tickets.**

  the agent finds the document, reads its text, and drafts one issue per requirement in your tracker, quoting the brief rather than paraphrasing from memory.

  tools: `drive_search_files` -> `drive_read_file_content` -> `jira_create_issue`

- **pull the latest export and load it into the room's database.**

  it downloads the raw file onto the room server and imports it with the database client installed there, so the data never leaves the room.

  tools: `drive_search_files` -> `drive_download_file_content` -> `bash`

- **which files in the client folder are shared outside the company?**

  it lists the folder, reads each file's sharing permissions, and reports the ones open to anyone with the link. nothing is changed in the process.

  tools: `drive_search_files` -> `drive_get_file_permissions` -> `drive_get_file_metadata`

## what it will not do

there is no editing, no deleting, no moving, and no changing who a file is shared with. drive scopes are fixed once the connection exists, so widening them means reconnecting the room, and an agent cannot reach a drive the connected account was never given.

## faq

### can an ai agent read my google drive files?

yes, with the read and search files scope. drive_search_files finds them, drive_read_file_content reads text, and drive_download_file_content pulls raw bytes into the room so an agent can work from a spec or a dataset instead of a pasted excerpt.

### can it create or change documents?

drive_create_file and drive_copy_file are behind the create and copy files scope and both ask before they run. there is no tool that edits or deletes an existing file, so the worst an approved call can do is add something new to the drive.

### how does the agent know who a file is shared with?

drive_get_file_permissions reads a file's sharing permissions and drive_get_file_metadata reads the rest of its metadata. that is how an agent can flag a document that is shared more widely than it should be before anyone quotes from it.

### is google drive available on every room?

google drive is gated per room and turned on by request. until access is granted for a room, the connector shows a request link instead of an authorise button, so the drive tools do not exist for that room's agents at all.

### does connecting drive in one room expose it to my other rooms?

no. the credential is stored against the room it was authorised in. another room in the same team sees no drive tools until someone connects it there, which is what keeps one client's documents out of another engagement.