Skip to main content
Per-app Google setup is deprecated. All Google apps now share one Google OAuth client and one Redirect URI. To use your own client, follow the Google setup guide. Credentials saved for one Google app apply to all of them.

​
Overview

OneCLI connects AI agents to Google Slides through Google’s OAuth flow. Agents can read presentation content, create new slide decks, and edit existing ones. The gateway injects OAuth credentials into requests to the Google Slides API automatically. This is useful for agents that generate presentations from data, update slide content programmatically, or extract information from existing decks.

​
What you will set up

  • A Google OAuth client shared by every Google app in OneCLI
  • A Google Slides connection authorized with your account
  • Per-agent, per-tool access to presentations

​
Connect Google Slides

This applies on OneCLI Cloud and self-hosted alike. One Google client serves every Google app in OneCLI, so you set it up once. If you already did it for another Google app, skip to step 2.

1. Set up your Google client

Follow the Google setup guide. It enables the Google APIs, sets up the consent screen, creates the OAuth client, and adds the Redirect URI.
Open Connections > Google Slides, select Connect Google Slides, pick your Google account, and click Allow.
OneCLI connect window for Google Slides showing Configuration required, the setup guide link, and the Configure credentials button.

The Google Slides connect window before a Google client is set up.

​
What agents can do

  • Read presentation structure (slides, layouts, masters)
  • Get text content from all slides in a presentation
  • Create new presentations with a specified title
  • Add new slides with chosen layouts
  • Insert, replace, or delete text on slides
  • Add and position shapes, images, and tables
  • Apply text formatting (font, size, color, bold, italic)
  • Duplicate, reorder, and delete slides
  • Read and modify speaker notes
  • Replace placeholder text and images across all slides

​
Controlling access

Access is per agent: grant the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization rules add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches Google Slides.

​
FAQ

Yes. Follow the Google setup guide once. One client serves every Google app in OneCLI.
No. The token stays in OneCLI, and the gateway adds it at the proxy. See How it works.
Yes. A read-only agent is a single grant.