Files and knowledge
Google Slides for AI agents.
Managed auth, ready-made tools.
Create presentations, add slides and replace text in Google Slides on behalf of each of your users.
About Google Slides
With the Google Slides connector, your agent works in each user’s own presentations. It can create a presentation, read its slides, add or delete a slide and replace text across a deck, using only the tools your project allows.
Google Slides is a presentation app in Google Workspace for building and sharing slide decks.
Tools
What your agent can do in Google Slides.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Google Slides connection.
-
Create a presentation
Writegoogle_slides_create_presentationCreate a new, empty presentation.
-
Get a presentation
Readgoogle_slides_get_presentationRead a presentation and the content of its slides.
-
Get a slide
Readgoogle_slides_get_slideRead the content of a single slide.
-
Add a slide
Writegoogle_slides_create_slideAdd a new slide with a chosen layout.
-
Replace text
Writegoogle_slides_replace_textReplace every match of a text across the deck.
-
Delete a slide
Writegoogle_slides_delete_slideRemove a slide from a presentation.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Google Slides, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read decks and add slides, and switch off
google_slides_delete_slideso it can never remove a slide. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example reading presentations but not editing them. A call outside them is refused.
Get started
Connect Google Slides
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Google Slides
Each end user authorizes their own Google Slides account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Google Slides account, once. const connection = await agent200 .user("user_123") .connect("google_slides"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Google Slides tools
Name the user, the model and the tools. The model decides which Google Slides tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Create a deck for Monday's team update", tools: ["google_slides"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Google's own sign-in page. You never see or store their Google password.
-
What access is requested
The scopes the connection needs, such as reading presentations or editing presentations, listed on Google's authorization screen. Users can remove the app later from their Google account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Google Slides connector and how to use it.
Connector: Google Slides, through Agent200. In code: "google_slides". What it does: Create presentations, add slides and replace text in Google Slides on behalf of each of your users. Page: https://www.agent200.com/connectors/google-slides/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Google Slides's own page, through the authorization link Agent200 returns. Never ask a user for a Google Slides password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: google_slides_get_presentation, google_slides_get_slide. Write tools: google_slides_create_presentation, google_slides_create_slide, google_slides_replace_text, google_slides_delete_slide. Name "google_slides" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/google-slides/framework/claude/ https://www.agent200.com/connectors/google-slides/framework/chatgpt/ https://www.agent200.com/connectors/google-slides/framework/claude-code/ https://www.agent200.com/connectors/google-slides/framework/muse/ https://www.agent200.com/connectors/google-slides/framework/grok-bot/ https://www.agent200.com/connectors/google-slides/framework/openai-dots/ https://www.agent200.com/connectors/google-slides/framework/claude-duet/ https://www.agent200.com/connectors/google-slides/framework/hermes-agent/ https://www.agent200.com/connectors/google-slides/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/google-slides.md
Guides
Use Google Slides with the AI you build on.
Step-by-step setup for Google Slides with a specific model, assistant or agent framework.
-
Google Slides + Claude
How to connect Google Slides to Claude
-
Google Slides + ChatGPT
How to connect Google Slides to ChatGPT
-
Google Slides + Claude Code
How to connect Google Slides to Claude Code
-
Google Slides + Muse
How to connect Google Slides to Muse
-
Google Slides + Grok Bot
How to connect Google Slides to Grok Bot
-
Google Slides + OpenAI Dots
How to connect Google Slides to OpenAI Dots
-
Google Slides + Claude Duet
How to connect Google Slides to Claude Duet
-
Google Slides + Hermes Agent
How to connect Google Slides to Hermes Agent
-
Google Slides + OpenClaw
How to connect Google Slides to OpenClaw
FAQ
Google Slides and Agent200, answered.
Who handles the Google Slides OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Google Slides.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Google Slides connection, never another user's. It cannot reach anything the user or Google Slides has not authorized.
Can I limit what my agent can do in Google Slides?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.