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.
Interactive. No signup. 14 days free · approvals always free.
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
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
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.
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, and no surprise send you find out about after it's already out the door.
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.
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.
What wakes Rills up in Google Slides
When these events fire, Rills proposes the next move and waits for your call.
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.
What Rills can do in Google Slides
2 of 8 actions across reads, writes, and updates.
- 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.
- 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.
Common questions about Google Slides automation
How do I automate Google Slides presentation creation from a template?
Rills can copy a Google Slides template, populate it with your data, and queue the result for your review before anything gets shared or sent. You approve the new deck from your phone. The AI proposes; nothing ships until you say so.
Can I get mobile approval before a new Google Slides deck is created?
Yes. Every proposed Google Slides action, including creating or updating a presentation, sits in your mobile approval queue first. You swipe to approve or reject from your phone before Rills does anything to your actual files.
How do I automatically build Google Slides from Markdown content?
Rills can watch a trigger, take your Markdown content, and propose a fully structured Google Slides presentation. You review the proposed slides before they get created. If the structure looks wrong, you reject it and nothing gets written to your Drive.
Can Rills auto-update a Google Slides deck when a new slide is added?
Rills listens for the slide-added event and can propose follow-up actions, like batch-updating the presentation or grabbing a fresh thumbnail for review. You decide what fires and what waits for your call before it touches the deck.
How do I schedule Google Slides creation without watching a dashboard?
You set the trigger condition and the action Rills should propose. When it fires, the action lands in your approval queue. You do not babysit a dashboard; you get a notification and approve or reject from wherever you are.
How is Rills different from Zapier for Google Slides automation?
Zapier executes actions the moment conditions are met. Rills proposes the action and waits for your approval before anything ships. For Google Slides, that means a deck does not get created, copied, or updated until you have seen exactly what the AI intends to do.
Does Rills support Google Slides event triggers for automation?
Yes. Rills supports the slide-added trigger for Google Slides. When a new slide appears in a monitored presentation, Rills can propose a downstream action, like updating the deck or copying it to a new file, and hold it for your approval before it runs.
How much does Google Slides automation cost with Rills?
Approvals and workflow logic are free. You only pay for real actions, meaning actual AI calls and the work of writing to or reading from Google Slides. Reviewing a proposed deck creation on your phone costs you nothing. You pay when the action runs, not when you decide.