Skip to main content
Integrations · Google Slides
Guild agents can read Google Slides presentations and apply batch updates without any manual token handling. OAuth tokens refresh automatically, and credentials are injected server-side so agent code never sees them. Credential policies let you restrict which operations each agent can perform before any request reaches Google.

Book a demo

See how teams govern agents that use Google Slides.

Start free

Connect Google Slides and scope your first agent.

What the Google Slides integration exposes

The integration provides tools that cover creating presentations, retrieving full presentations or individual pages, generating page thumbnails, and applying batch updates. Tools use the google_slides_oauth_ prefix and are imported from the @guildai-services/guildlabs~google-slides-oauth package. Use pick() from the Agent SDK to give each agent only the tools it needs.

How it works

1

Open Credentials in Guild

Go to Credentials in Guild under Access & setup. This is where all third-party service connections are managed.
2

Authorize your Google account

Click Google Slides and complete the OAuth authorization with your Google account. Guild stores the credential and refreshes the token automatically.
3

Import tools into your agent

Spread GoogleSlidesOauthTools into your agent’s tools object, or use pick() to include only the specific tools your agent requires.

Why Google Slides access needs governing

Batch update operations can modify any presentation the connected Google account can reach. Guild’s credential policies let you write ALLOW and DENY rules that the credential proxy enforces before any request leaves Guild. You can restrict specific operations by name or pattern, scope rules to individual agents or workspaces, and block write operations while permitting reads, all on a single connected credential. Credentials are stored and injected server-side, so agent code, prompts, and containers never see the OAuth token. You can scope a credential to one workspace, one member, or a single agent using Guild’s credential scoping options. An agent that should only read presentations never gains access to batch update unless a policy explicitly allows it.

About the Google Slides integration

The @guildai-services/guildlabs~google-slides-oauth package gives your agents access to Google Slides presentations through Guild’s Google Slides integration.

Authentication

  • Type: OAuth 2.0
  • Token management: Refreshed automatically

Setup

1

Open Credentials

Go to Credentials in Guild.
2

Connect Google Slides

Click Google Slides and authorize with your Google account.

Usage

Selecting specific tools

Tools are named with the google_slides_oauth_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildlabs~google-slides-oauth:

Frequently asked questions

Yes. Use a credential policy with a DENY rule targeting google_slides_oauth_batch_update_presentation and an ALLOW rule for the read tools. The credential proxy enforces the rule before any request reaches Google.
No. The catalog entry for guildlabs~google-slides-oauth lists no webhook events, so the integration does not receive or emit real-time change notifications from Google Slides.
Guild refreshes OAuth tokens automatically. The page states token management is handled server-side, so agents continue making calls without any manual re-authorization.
Yes. Connect a credential dedicated to that agent from the installed agent’s page, or use credential policies scoped to that agent’s ID. Other agents in the workspace will not use a dedicated credential that belongs to a single agent.

Put a governed agent on Google Slides this week

Book a demo

See how teams govern agents that use Google Slides.

Start free

Connect Google Slides and scope your first agent.
Also runs on Guild: Google Docs · Google Drive · Google Sheets · Notion Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on October 16, 2026