Sign inStart your trial

Google SlidesGoogle Slides
01Integration field card

Google Slides Automation, Approvals & Workflows

Run Google Slides on autopilot. Keep the veto.

8 actions1 trigger

A slide deck ships to a client before you've seen the final copy, because a triggered workflow fired without your sign-off. Rills proposes every change; you approve before it goes out.

Try the approval demo

Interactive. No signup. 14 days free · approvals always free.

Powered by Composio
02. The trust layer

Most automation fires first, asks later. Rills shows you the change before it ships.

Every consequential other action from Google Slides arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.

Queue 3

GOOGLE SLIDES · DECK BUILD
72

Create 3 client decks from the Q3 proposal template?

3 presentations · template last updated 6 days ago

Same run pattern as the June client batch

One source file has unresolved comment threads

SWIPE → APPROVE
Illustrative. Your real proposals match your data and your approval history.
  1. Free to wait. Free to think.

    Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.

  2. Approve from your phone in five seconds.

    Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, no 3am stomach-drop wondering what shipped while you slept.

  3. Routine cases graduate themselves.

    Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.

03. Overview

About Google Slides automation

Presentation decks go out with wrong data, stale copy, or the wrong template applied, because the workflow that built them didn't wait for your call.

When Google Slides runs unsupervised

Automation that writes directly into your presentations can fire on the wrong input and send something you'd never have approved yourself.

  • Create Google Slides Presentation fires with a mismatched template and a client receives a deck branded for a different account.
  • Copy Google Slides from Template runs on stale source data and ships slides with last quarter's numbers still in them.
  • Create Slides from Markdown converts a draft that wasn't ready, posting unreviewed copy into a deck already shared with stakeholders.
  • Update Presentation (Batch/Markdown) overwrites sections you'd marked for manual review, and the change goes out before you notice.

What Rills does inside Google Slides

Rills sits between the trigger and the action. When a new slide is added or a template copy is queued, Rills surfaces the proposed Google Slides automation step, including which presentation is targeted and what content will be written, before a single slide changes.

The deck still gets built; you just see exactly what it will contain before it ships.

When Google Slides events should and shouldn't act on their own

The GOOGLESLIDES_SLIDE_ADDED_TRIGGER fires whenever a slide is added to a presentation, but not every addition carries the same risk. Some are safe to approve Google Slides changes on automatically once the pattern is established; others should always wait.

  • GOOGLESLIDES_SLIDE_ADDED_TRIGGER (internal draft deck): Routine additions to a known internal template are low-risk and can graduate to autonomous once the pattern repeats cleanly.
  • GOOGLESLIDES_SLIDE_ADDED_TRIGGER (client-facing deck): Any addition to a presentation shared externally should wait for your review; a wrong slide in front of a client is hard to walk back.
  • GOOGLESLIDES_SLIDE_ADDED_TRIGGER (templated batch run): When the trigger fires as part of a bulk create-from-template job, each deck in the batch deserves a single grouped approval before the whole set goes out, not one silent approval per file.
04. Triggers

What wakes Rills up in Google Slides

When these events fire, Rills proposes the next move and waits for your call.

  • webhook

    GOOGLESLIDES SLIDE ADDED

    Triggers when someone adds a new slide to a Google Slides presentation. Use this to automatically sync slide changes with other tools or notify collaborators of presentation updates.

05. Actions

What Rills can do in Google Slides

2 of 8 actions across reads, writes, and updates.

  1. 01

    Create Google Slides Presentation

    Creates a new blank Google Slides presentation that you can customize with your content. Use this to quickly generate presentations for client proposals, reports, or team collaboration.

  2. 02

    Create Slides from Markdown

    Transforms Markdown text into a formatted Google Slides presentation, automatically organizing content into slides and applying templates based on your content structure.

06. FAQ

Common questions about Google Slides automation

07. NEXT MOVE

Approve every Google Slides change before it ships.

14 days free. No credit card. About 90 seconds to your first proposal.