FlowRunner
Pricing
Theme

Google Slides

Documents

Create and manage Google Slides presentations, fill slides, run template-based deck generation, and export to PDF, PPTX, or thumbnail images through the Google Slides and Drive APIs. Agents generate customer-ready decks from workflow data.

12 actions available
A record needs a deck (new customer, monthly review, generated report)
Agent pulls the values the template expects from the source system
Create From Template copies the deck and replaces every {{placeholder}} token
Get Slide Thumbnail renders a preview PNG of the first slide into FlowRunner file storage
Agent posts the preview to the owning channel for a quick look
Export Presentation renders the finished deck to PDF into FlowRunner file storage
Client-facing decks pause for an owner to approve before the export is sent outside the company

What This Integration Enables

Agents can build and manage presentations as steps inside a workflow. The most common pattern is template-based deck generation: copy a template presentation, replace tokens with real data, and export the result. Agents can also create decks from scratch, add slides from predefined layouts, insert text boxes at precise positions, swap placeholder shapes for images from a URL, and render slide thumbnails as hosted PNGs for previews and approvals. Advanced operations reach the Slides API through the raw Batch Update passthrough. The value is not that FlowRunner can edit a slide. The value is that producing a customer-ready deck stops being a person's repeat chore and becomes a governed step, with a human pulled in only when the deck is about to go to a customer.

Without FlowRunner

One deck at a time Someone copies last quarter's deck and swaps names and numbers by hand for each client
No preview before send The finished deck is judged only after it is fully exported and opened
Manual export and archive Each deck is exported and filed wherever the person was working

With FlowRunner

Generated from record data The agent fills every placeholder from the source system in one step
Thumbnail preview inline A rendered slide preview lands in the channel before anything is exported or sent
Consistent PDF or PPTX handoff Every deck lands in FlowRunner file storage ready for the next step

Use Case Scenarios

Per-customer decks generated in bulk

A quarterly review cycle needs a personalized deck for every account. The agent reads per-customer rows from [Google Sheets](/integrations/google-sheets), then calls Create From Template for each row, filling the `{{placeholders}}` with that customer's name, metrics, and next steps. It runs Export Presentation to produce a PDF in FlowRunner file storage and emails the edit link through [Gmail](/integrations/gmail-service). The account team stops rebuilding the same deck by hand for every client and starts reviewing generated drafts instead.

Starter deck from an inbound request

An inbound email arrives with content that needs to become a presentation. The agent creates a new deck with Create Presentation, adds slides with Add Slide, and places the content with Insert Text Box. It then calls Get Slide Thumbnail to render a preview PNG and posts that image into a [Slack](/integrations/slack) message so the team can react to the layout before anyone opens the full file. The blank-page work is done; the humans start from a draft.

Branded deck with a human gate before it ships

A finished deck is generated for an external audience, complete with the customer's logo swapped in through Replace Text With Image. Because the deck is going to a customer, the agent does not export and send it automatically. It renders a thumbnail, posts it for the owner to review, and waits. Once the owner approves, the agent runs Export Presentation and hands the PDF to the next step. The routine assembly is automated; the decision to put the deck in front of a customer stays with a person.

Human-in-Loop Highlight

The consequential moment with Google Slides is sending a generated deck to a customer, not building it. Before an agent exports and forwards a client-facing presentation, it pauses and posts a rendered slide thumbnail to the owner through Slack: "The [Company] review deck is generated and ready. Here is a preview of the title slide. Approve to export and send, or tell me which slide to fix?" The owner sees exactly what a customer would see and approves or corrects. A deck with the wrong number on slide three is a deck that goes to a client with the wrong number, so the agent treats the export-and-send as the point that needs human judgment.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via Slack
Human decides
Agent resumes with decision

Agent Capabilities

12 actions

Presentations

5
  • Create Presentation Creates a new, blank presentation with a given title in the connected user's Drive, containing one default title slide. Used when a workflow needs to build a deck from scratch rather than from a template.
  • Get Presentation Retrieves a presentation and returns a summary with title, revision ID, page size, slide count, and a per-slide list, optionally including the full raw resource. Used to inspect a deck's structure before editing it or to confirm its contents.
  • Create From Template Copies an existing template presentation through the Drive API and replaces `{{placeholder}}` tokens across all slides, returning the occurrence count replaced per placeholder. This is the primary action for generating customer-ready decks from workflow data.
  • Export Presentation Exports a presentation to PDF or PowerPoint (PPTX) through the Drive API, saves it to FlowRunner file storage, and returns a hosted URL. Used at the end of a generation workflow to produce a shareable file; Drive export is limited to 10 MB of content.
  • Delete Presentation Permanently deletes a presentation from Google Drive, skipping the trash. This cannot be undone. Used in cleanup workflows for temporary decks the agent created earlier in the same flow.

Slides

3
  • Add Slide Adds a new slide using one of the predefined layouts, optionally at a specific position, and returns the new slide's object ID. Used when building a deck programmatically slide by slide.
  • Delete Slide Deletes a slide or page element by its object ID, removing all of its content; a presentation must keep at least one slide. Used to prune slides that do not apply to a given audience.
  • Get Slide Thumbnail Renders a thumbnail of a single slide, saves it as a PNG to FlowRunner file storage, and returns a hosted URL with dimensions. Used to post a visual preview for review or approval before a deck is exported and sent. Thumbnail generation counts as an expensive read against the Slides API quota.

Content

3
  • Insert Text Box Inserts a new text box with given text onto a slide, with position and size in points. Used to place content at a precise spot when building or filling a deck.
  • Replace All Text Finds and replaces every occurrence of a text string across all slides, in shapes and tables, returning the number of occurrences changed. Commonly used to fill `{{placeholder}}` tokens across a deck.
  • Replace Text With Image Replaces shapes containing a given text with an image fetched from a public URL, across all slides, inheriting each replaced shape's size and position. Used to swap placeholder shapes for logos, charts, or product photos.

Advanced

1
  • Batch Update Applies a raw list of Slides batchUpdate requests atomically, the escape hatch for operations not covered by dedicated actions such as styling text, creating tables, duplicating slides, and updating speaker notes. Used when a workflow needs an advanced Slides operation.

Start building with Google Slides

$100 in credits. No card required. Connect in minutes.