DashboardSign inStart your trial

Google DriveGoogle Drive
01Integration field card

Google Drive Automation, Approvals & Workflow

Run Google Drive on autopilot. Keep the veto.

90 actions7 triggers

Files get shared, deleted, and overwritten in Google Drive before you realize what went out. Rills proposes each action, you approve before anything ships.

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 Drive arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.

Queue 3

GOOGLE DRIVE · PERMISSION REVIEW
72

Grant editor access to 3 client folders for new contractor?

3 folders flagged · permissions change triggers fired in last 2h

Contractor email not seen in any previous approved grant

Same folder set had an accidental public link last month

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, and no surprise send you find out about after it's already out the door.

  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 Drive automation

Files disappear, permissions go wide open, and shared drives get restructured in Google Drive automation workflows before anyone notices the mistake sitting in someone's inbox.

When Google Drive runs unsupervised

The wrong version ships, the wrong person gets access, and by the time you catch it the file is already open in three browsers.

  • Upload/Update File Content fires on the wrong revision, overwriting a client deliverable you hadn't signed off on.
  • GOOGLEDRIVE_FILE_SHARED_PERMISSIONS_ADDED adds a viewer or editor to a sensitive folder before you've confirmed who should see it.
  • Delete file runs on a file that matched the query pattern but wasn't the one you meant to remove.
  • Create Shared Drive provisions a new shared space and sends invites before you've set the access policy.
  • GOOGLEDRIVE_FILE_DELETED_OR_TRASHED_TRIGGER fires a downstream action the moment a file moves to trash, which may have been an accident.

What Rills does inside Google Drive

Rills watches for file creation, permission changes, and content updates, then queues a proposal for each one instead of acting. Before a Resumable Upload completes or a shared drive gets created, you see exactly what is about to happen and you decide.

The file still gets shared; you just approve it before it goes out.

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

Not every trigger carries the same risk. Some are routine enough to graduate toward autonomous; others should always wait for your call.

  • GOOGLEDRIVE_FILE_CREATED_TRIGGER: Routine enough to act autonomously when the file matches a known naming pattern in a low-stakes folder.
  • GOOGLEDRIVE_NEW_FILE_MATCHING_QUERY_TRIGGER: Routine for archiving or tagging actions where no external person is affected.
  • GOOGLEDRIVE_GOOGLE_DRIVE_CHANGES: Safe to act autonomously for internal logging or change-tracking notifications with no write consequences.
  • GOOGLEDRIVE_FILE_SHARED_PERMISSIONS_ADDED: Always needs a human; a wrong permission grant reaches a real person instantly.
  • GOOGLEDRIVE_FILE_UPDATED_TRIGGER: Needs a human when the update touches a client-facing or contractual document.
  • GOOGLEDRIVE_FILE_DELETED_OR_TRASHED_TRIGGER: Needs a human; deletions are hard to reverse and the trigger can fire on accidental trashes.
04. Triggers

What wakes Rills up in Google Drive

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

  • webhook

    GOOGLEDRIVE COMMENT ADDED

    Fires when someone adds a new comment to a Google Doc, Sheet, or Slide. Use this to track discussions and feedback on your documents.

  • webhook

    GOOGLEDRIVE FILE CREATED

    Fires when a new file is created or uploaded to Google Drive. This triggers immediately upon detection of the new file.

  • webhook

    GOOGLEDRIVE FILE SHARED PERMISSIONS ADDED

    Fires when a file or folder in Google Drive is shared with new people or groups. This helps you stay informed whenever access permissions are granted.

  • webhook

    GOOGLEDRIVE FILE UPDATED

    Fires when a file's content or details (like name or description) change in Google Drive. You'll receive information about who made the change and when.

  • webhook

    GOOGLEDRIVE NEW FILE MATCHING QUERY

    Fires when a new file is created in Google Drive that matches specific search criteria you define. Use this to automatically act on files of a certain type, name, or folder.

05. Actions

What Rills can do in Google Drive

4 of 90 actions across reads, writes, and updates.

  1. 01

    Create Permission

    Share files or folders with specific people, groups, or make them publicly accessible by setting granular permissions on your Google Drive items.

  2. 02

    Create a folder

    Creates a new folder in Google Drive, either at the root level or within an existing parent folder, allowing you to organize and structure your cloud storage hierarchy.

  3. 03

    Download a file from Google Drive

    Downloads files from Google Drive to your computer, with the ability to convert Google Docs, Sheets, and Slides into different formats like text, CSV, or PDF. Use this to retrieve documents you've stored in the cloud and save them locally or integrate them into your workflows.

  4. 04

    Find file

    Search and locate files and folders across Google Drive using flexible search criteria like names, dates, file types, and custom properties. Quickly find the documents you need without manual browsing through your entire Drive.

06. FAQ

Common questions about Google Drive automation

How do I automate Google Drive file uploads without losing control?

Rills watches your Drive for changes and proposes the upload or update action before anything writes to your files. You approve from your phone. Nothing overwrites a folder or file until you say so, and the workflow logic that decides when to act is free.

Can I get mobile approvals before Rills deletes or trashes a Google Drive file?

Yes. Delete and trash operations go into your mobile approval queue first. You review the proposed action on your phone, see which file is targeted and why, and either approve or reject it. The file stays untouched until you make the call.

How do I trigger a workflow when a new file is shared in Google Drive?

Rills listens for the file-shared-permissions event on your Drive. When someone gains access to a file you care about, Rills can propose a follow-up action, like updating metadata or notifying a channel, and wait for your approval before anything ships.

Can Rills automate Google Drive folder and Shared Drive management?

Rills can create, update, or hide Shared Drives as part of a workflow. Those actions sit in your approval queue before they execute. Routine ones can graduate to autonomous over time as the confidence score learns your patterns, but you keep the veto until you are ready.

How do I automate Google Drive actions when a file matches a specific query?

The new-file-matching-query trigger fires when a file meets criteria you define, like a name pattern or folder location. Rills proposes what to do next, whether that is editing the file, updating a property, or moving it, and holds for your approval before it touches anything.

How is Rills different from Zapier for Google Drive automation?

Zapier executes the moment conditions are met. Rills proposes the action and waits for you to approve it, from your phone, before anything ships. If an AI-suggested edit or delete is wrong, you catch it before it causes damage, not after you find it in a support thread.

Does Rills support Google Drive webhooks and change tracking?

Rills connects to Drive change events directly, covering file creation, updates, deletions, comment additions, and permission changes. You do not set up any technical connection yourself. Rills handles the listening; you just decide what happens when an event fires.

How much does Rills cost for Google Drive automation?

Approvals and all workflow logic are free. You only pay when Rills executes a real action, like an API call to create a Shared Drive, upload file content, or edit a file. Reviewing proposed actions on your phone and deciding whether to approve costs nothing.

07. NEXT MOVE

Approve every Google Drive change before it ships.

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