Google Slides
for LuumenAI
Read your decks for context, then draft and update slides as approved steps
Connect Google Slides and Luumen can read the decks your team already maintains — the incident review template, the monthly platform report, the change board summary. It pulls slide content and layout for context, then builds new decks or updates existing ones. Changes are previewed and held for your approval before anything is written.
The Google Slides toolbox
7 tools: 3 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Page Thumbnail v2Generate a thumbnail of the latest version of a specified page.
- ReadGet PresentationRetrieve the latest version of a presentation.
- ReadGet Presentation PageGet the latest version of a specific page in a presentation.
- WriteCreate Google Slides PresentationCreate a blank Google Slides presentation. Approval by default
- WriteCreate Slides from MarkdownCreates a new Google Slides presentation from Markdown text. Approval by default
- WriteUpdate Presentation (Batch/Markdown)Update Google Slides presentations using markdown content or raw API text. Approval by default
- WriteCopy Google Slides from TemplateCreate a new Google Slides presentation by duplicating an existing template deck via Drive file copy. Approval by default
One prompt, start to finish
What a governed Google Slides run looks like inside Luumen.
Questions
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create google slides presentation, create slides from markdown, update presentation (batch/markdown), copy google slides from template — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Google Slides — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
ConfluenceSOPs and runbooks that become skills the whole team can run.
NotionRunbooks in Notion, followed and turned into skills.
SharePointRead SharePoint sites for context, then change files and permissions on approval.
Google DriveSearch Drive for the file you need, then write the change back as an approved stepPut Google Slides to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.