Runner
Google Slides logo

Google Slides Runner Workflows

Build the deck from live context instead of rewriting slides by hand.

Runner's public Slides workflows are backed by the same Google Drive presentation tools used in the Electron backend, so deck creation and updates stay connected to the source docs.

GooglePresentations
What would you like to do?
01

What Runner actually does with Google Slides

This page is tied to the real connector definition inside Runner. The highlights below describe the kinds of actions, safeguards, and workflow patterns the app page represents, not a generic integration directory blurb.

Create a deck shell from the workflow itself.

Translate a working brief into a Slides narrative.

Update the presentation programmatically when the story changes.

Backend surface

Composio toolkit via Drive powers this connector inside Runner. Slides automation is currently implemented in `google-drive.ts`, where Runner exposes presentation create, read, update, and doc-to-deck flows.

Operational notes

  • The same backend tooling that manages Drive files currently owns Slides presentation updates.
  • This page is grounded in the real presentation actions exported from the Drive tool-config module.
02

Popular workflows with Google Slides

Real workflow pages where Google Slides is part of the connected stack. Each workflow shows the trigger, connectors, and outcome.

AI Board Prep for Founders

AI Board Prep for Founders

A board-ready deck drafted in minutes instead of a weekend.

Google Slides logoGoogle SlidesNotion logoNotionGmail logoGmailLinear logoLinear

Customize Demo Deck for Prospect Meetings

Customize Demo Deck for Prospect Meetings

A personalized demo ready 24 hours before every call.

Google Slides logoGoogle SlidesHubSpot logoHubSpotGmail logoGmail
03

Connect Google Slides to your favorite apps

Apps that show up alongside Google Slides in real Runner workflows. Each badge links to its own integration page.

Gmail logoGmail
HubSpot logoHubSpot
Linear logoLinear
Notion logoNotion
04

Triggers and actions

What Runner can do with Google Slides. These are grounded in the real backend connector definitions, not generic marketing filler.

Generate a deck from the brief

GOOGLEDRIVE_DOC_TO_SLIDES_BRIEF

Convert a Google Doc into a Google Slides briefing deck.

“Turn the stakeholder research brief into a first-pass slides deck for tomorrow's meeting.”

Runner moves from working doc to actual presentation without a manual deck rebuild.

Create the presentation shell

GOOGLEDRIVE_CREATE_PRESENTATION

Create a new Google Slides presentation and optionally place it in a folder.

“Create a new customer-deck shell in the Acme folder before we customize the story.”

The presentation exists in the right place before anyone starts editing slides.

Inspect the current deck structure

GOOGLEDRIVE_GET_PRESENTATION

Get Slides metadata including title, slide count, and slide object IDs.

“Read the current deck structure so we can update the problem, solution, and rollout slides.”

Runner can target the right deck elements before applying changes.

Apply slide changes programmatically

GOOGLEDRIVE_UPDATE_PRESENTATION

Apply programmatic edits to a Google Slides presentation through the Slides batchUpdate API.

“Update the narrative to focus on rollout predictability and edit slides 3 through 6.”

The deck changes reflect the latest account context without manual slide-by-slide work.

Use Google Slides inside a real workflow

Start with Gmail, tell Runner you work in Google Slides, and it will tee up the right first workflows before the desktop install handoff.

More apps