Integrations · Google Drive
A Guild agent can list, read, create, copy, update, and delete files and folders in Google Drive, manage permissions and comments, and watch for changes. Guild stores the OAuth 2.0 token server-side and refreshes it automatically, so agent code never handles credentials directly. Credential policies let you restrict which Drive operations each agent can call, and every request passes through Guild’s audit trail.
Book a demo
See how teams govern agents that use Google Drive.
Talk to sales
Get access to Guild, then connect Google Drive to your first agent.
What the Google Drive integration exposes
The tools cover files, folders, shared drives, permissions, comments, replies, revisions, labels, and change tracking. Agents can copy files, modify labels, manage trash, generate file IDs, watch files or changes, and stop watch channels. Tools follow thegoogle_drive_ naming prefix and can be narrowed with pick() so an agent receives only the operations it needs.
How it works
1
Open Credentials in Guild
Go to Credentials in Guild. The page lists connected credentials and shows a gallery of available integrations.
2
Authorize your Google account
Click Google Drive and complete the OAuth authorization. Guild stores the token server-side and refreshes it automatically.
3
Import and scope the tools
Import
GoogleDriveTools from the package and spread it into your agent’s tools object. Use pick() to include only the specific tools your agent needs.Why Google Drive access needs governing
Google Drive credentials in Guild are scoped at the account, workspace, member, or agent level. An account credential serves every workspace the account owns by default. You can dedicate a credential to a single agent or restrict a workspace to use only its own credentials, so Drive access never crosses workspace boundaries unintentionally. See Credentials for the full scoping model. Guild’s credential proxy enforces credential policies before any request reaches Google Drive. ALLOW and DENY rules target specificgoogle_drive_ operations by name or glob pattern. A DENY rule always wins over an ALLOW rule, and rules can be scoped to specific agents or workspaces on the same credential. Agent code never sees the OAuth token; Guild injects it server-side only after the policy check passes. Teams that need read-only Drive access can deny all write and delete operations on the shared credential while granting a dedicated agent broader rights.
About the Google Drive integration
The@guildai-services/guildlabs~google-drive package gives your agents access to files and folders in Google Drive through Guild’s Google Drive integration.
Authentication
- Type: OAuth 2.0
- Token management: Refreshed automatically
Setup
1
Open Credentials
Go to Credentials in Guild.
2
Connect Google Drive
Click Google Drive and authorize with your Google account.
OAuth scopes
Scopes Guild requests in the latest published version ofguildlabs~google-drive:
Usage
Selecting specific tools
Tools are named with thegoogle_drive_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildlabs~google-drive:
All 42 tools
All 42 tools
Frequently asked questions
Does the integration support webhook events from Google Drive?
Does the integration support webhook events from Google Drive?
Not yet. The catalog entry for this integration lists no webhook events. The
google_drive_watch_changes and google_drive_watch_file tools let an agent register watch channels, but Guild does not currently deliver inbound Drive webhook payloads as event triggers.How do I limit an agent to read-only access on Drive?
How do I limit an agent to read-only access on Drive?
Write a credential policy that denies operations matching patterns such as
*_create, *_update, *_delete, *_copy, and google_drive_empty_trash, then adds a catch-all ALLOW. The proxy enforces the policy before any request leaves Guild. See Credential policies for syntax and examples.Can I give one agent its own Drive credential separate from the rest of the organization?
Can I give one agent its own Drive credential separate from the rest of the organization?
Yes. From the installed agent’s page, connect a credential dedicated to that agent. A dedicated credential is stored under the account that owns the workspace and never serves other agents or workspaces. See Credentials for steps.
Can I use this integration alongside other Google Workspace integrations?
Can I use this integration alongside other Google Workspace integrations?
Yes. Guild also provides integrations for Google Docs, Google Sheets, and Google Slides. Each is a separate package with its own credential and tools, so you can spread multiple tool sets into the same agent.
Put a governed agent on Google Drive this week
Book a demo
See how teams govern agents that use Google Drive.
Talk to sales
Get access to Guild, then connect Google Drive to your first agent.