Google Slides
Read presentations and update them.
A Google Slides connection gives a playbook's functions the Google Slides API, from a document Auto ships. You sign in to Google and allow Google Slides, and the connection acts as you: it reads the presentations you can read and changes the ones you can edit.
On Auto Cloud, available once Google's review of Auto completes; on a self-hosted runtime, with your own Google Cloud project, now.
What a playbook can do with Google Slides
- Read a presentation: its slides, their text and their tables.
- Update a presentation: insert and replace text, edit tables, and add, duplicate, move and delete slides.
The update takes the kinds of request that edit text, tables and slides; images, shapes, themes and animations are not among them. A function reads a presentation by its id, which your agent, a Google Drive connection's search, or the workflow's input gives it.
The tools, as the connection lists them
Tools that read: slides.presentations.get.
Tools that act: slides.presentations.batchUpdate.
An example workflow
The monthly review deck, filled before the meeting. A schedule trigger runs the workflow two days before the review. An interaction function copies the deck template into this month's folder through a Google Drive connection. Lookup functions read the month's figures from a Google Analytics connection and the month's spend from a Google Ads connection. A computation function shapes them into the tables the template's slides hold. A reasoning function writes the headline of each slide in the form the team uses, one sentence that says what the figure means. An interaction function replaces the template's placeholders and fills the tables through slides.presentations.batchUpdate. The presenter opens the deck in Slides, changes what they like, and presents; the run's history in Studio keeps what was written and the figures it came from.
How to connect Google Slides
- Sign in to Google and allow Google Slides. The consent screen shows the permissions listed below.
Then:
- Ask your agent to connect Google Slides to Auto, or open Settings, Agents, Connections in Auto Studio and choose Google Slides. On Auto Cloud, Studio lists Google Slides once Google's review of Auto completes.
- On the Studio page, check the service and its access, choose which playbooks may use the connection, and approve it.
- Have your agent check one small read through the connection before a function depends on it.
What it needs
- A Google account, personal or Workspace, with access to the presentations the playbook reads and edit access to the ones it changes.
- Your agent connected to Auto and signed in as you, with permission to change your organization, if your agent adds the connection.
- On a self-hosted runtime, a Google Cloud project of your own with the Slides API enabled and an OAuth client registered for the runtime, as Let people add connections sets out.
Google grants Slides as a read scope and a read-and-write scope; the connection's operations delete no presentation, only slides within one, where a function names them.
Permissions Auto asks for
- See all Google Slides presentations.
- See, change, create and delete all Google Slides presentations.
Good to know
A presentation's text is kept in the run's history, where people with access to the playbook can read it. Build the deck from a copy of a template, so a run never edits the original.