Google Drive Automation, Approvals & Workflow
Run Google Drive on autopilot. Keep the veto.
89 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.
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 Drive arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue 3
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
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, no 3am stomach-drop wondering what shipped while you slept.
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 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.
What wakes Rills up in Google Drive
When these events fire, Rills proposes the next move and waits for your call.
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.
GOOGLEDRIVE FILE CREATED
Fires when a new file is created or uploaded to Google Drive. This triggers immediately upon detection of the new file.
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.
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.
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.
What Rills can do in Google Drive
4 of 89 actions across reads, writes, and updates.
- 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.
- 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.
- 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.
- 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.