Integrations · Google Sheets
A Guild agent reads, updates, and appends Google Sheets data on your behalf, using OAuth tokens that refresh automatically. Guild’s credential proxy injects authentication server-side, so the agent code never sees your token. Credential policies let you restrict exactly which spreadsheet operations each agent may perform.
Book a demo
See how teams govern agents that use Google Sheets.
Talk to sales
Get access to Guild, then connect Google Sheets to your first agent.
What the Google Sheets integration exposes
The tools cover reading and writing cell ranges, batch operations across multiple ranges, filtering by data filters, creating spreadsheets, copying sheets between spreadsheets, and managing developer metadata. Tools are prefixed withgoogle_spreadsheets_oauth_ 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 every service you can connect.
2
Authorize with Google
Click Google Sheets and complete the OAuth flow with your Google account. Guild stores the token and refreshes it automatically.
3
Add tools to your agent
Import
GoogleSpreadsheetsOauthTools and spread it into your agent’s tools object. Use pick() to include only the operations the agent needs.Why Google Sheets access needs governing
Guild’s credential proxy enforces credential policies before any request leaves Guild, so you can write ALLOW and DENY rules that restrict an agent to specific operations such as reads only, or block destructive clears entirely. Rules can be scoped to a specific agent or workspace, letting different agents share one connected credential while each operates under its own limits. Credentials are stored and injected server-side; agent code, containers, prompts, and state never see the OAuth token. You can scope a credential to a single agent, a single workspace, or a single member, and Guild’s resolution order ensures the most specific credential wins. That separation means revoking or rotating a credential takes effect immediately across every agent that used it, with no code change required.About the Google Sheets integration
The@guildai-services/guildlabs~google-spreadsheets-oauth package gives your agents access to Google Sheets spreadsheets through Guild’s Google Sheets integration.
Authentication
- Type: OAuth 2.0
- Token management: Refreshed automatically
Setup
1
Open Credentials
Go to Credentials in Guild.
2
Connect Google Sheets
Click Google Sheets and authorize with your Google account.
OAuth scopes
Scopes Guild requests in the latest published version ofguildlabs~google-spreadsheets-oauth:
Usage
Selecting specific tools
Tools are named with thegoogle_spreadsheets_oauth_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildlabs~google-spreadsheets-oauth:
Frequently asked questions
Can the integration receive webhook events when a spreadsheet changes?
Can the integration receive webhook events when a spreadsheet changes?
No. The catalog entry for this integration lists no webhook events, so agents cannot receive push notifications from Google Sheets.
How do I stop an agent from clearing data it should only read?
How do I stop an agent from clearing data it should only read?
Write a credential policy with a DENY rule targeting the clear and batch-clear operations, then add a catch-all ALLOW rule. Guild’s proxy enforces the DENY before the request reaches Google Sheets. See credential policies for rule syntax.
Does my agent code ever see the OAuth token?
Does my agent code ever see the OAuth token?
No. Guild’s credential proxy adds authentication server-side after the policy check passes. The token never enters the agent’s code, container, prompt, or state. See security architecture and credentials for details.
Can one connected credential serve multiple agents or workspaces?
Can one connected credential serve multiple agents or workspaces?
Yes. An account-scoped credential serves every workspace the account owns by default. You can then use credential policies to scope which operations each agent or workspace may perform on that shared credential, or connect a dedicated credential for a single agent if you need full isolation.
Put a governed agent on Google Sheets this week
Book a demo
See how teams govern agents that use Google Sheets.
Talk to sales
Get access to Guild, then connect Google Sheets to your first agent.