Google Drive
Files arrive, change, get filed, Drive as workflow input
Google Drive on Tiny Command treats the file system as an event source first and an API second. Three triggers cover the moments worth automating: File Created (a new file lands in a watched folder), File Updated (an existing file changes), Folder Created (a new subfolder appears). Each fires within seconds via Google's Drive push notifications. Eight actions cover the rest: List Files (with search query), Search Files (full-text against file content where Drive supports it), Get File (metadata or binary content), Create Folder, Copy File, Move File, Delete File, Share File (with email, link, or domain-wide sharing). The connection authorizes via Google OAuth with drive.file scope (only files Tiny Command creates or that you explicitly grant access to). Common patterns: a Gmail attachment lands as a File Created in Drive, an AI step extracts the contents, the result fans into Notion and Slack; or every uploaded design file routes via metadata into the correct customer folder.
Workflows start when Google Drive does.
3 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a new file is created in Google Drive (optionally scoped to a specific folder). Common use: ingest new docs into your CMS, OCR receipts, or alert the team when a contract drops.
Fires when a file in Google Drive is updated (content edited, renamed, moved, or re-shared). Used to re-index search, re-sync into your KB, or notify watchers.
Fires when a new folder is created in Google Drive (optionally scoped to a parent). Use for templated folder provisioning or governance audit logs.
Do anything Google Drive can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Copy File | Creates a copy of a file in Google Drive, optionally into a different folder and with a new name. Standard pattern for template-doc-per-customer flows. |
| Create Folder | Creates a new folder in Google Drive, optionally inside a parent folder. Used in onboarding workflows that auto-provision a workspace per customer. |
| Delete File | Permanently deletes a file or folder from Google Drive. Bypasses the trash; use Update File with trashed=true for the recoverable version. |
| Get File | Returns metadata for a specific Google Drive file or folder by ID: name, mimeType, parents, modifiedTime, size, and webViewLink. The standard read after a trigger fires with an ID. |
| List Files | Lists files and folders from Google Drive with optional Drive query (q parameter). Use to enumerate everything in a folder or to find files by name/mimeType. |
| Move File | Moves a file or folder to a different parent in Google Drive. Implemented as add new parent + remove old parent under the hood. |
| Search Files | Searches files and folders in Google Drive by name (uses a contains-match on the name field). For advanced queries, use List Files with a custom Drive q parameter. |
| Share File | Shares a Google Drive file or folder by creating a permission: type (user/group/domain/anyone), role (reader/commenter/writer), and emailAddress. Used for auto-granting access on customer signup. |
Pre-built Google Drive workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every Google Drive event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn Google Drive into a Notion-backed source of truth, auto-tagged.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Google Drive once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Google Drive field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Google Drive integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Google Drive to Tiny Command?
What Google Drive triggers does Tiny Command support?
What Google Drive actions can I run from a workflow?
Is the Google Drive integration real-time?
Do I need to write code to use Google Drive with Tiny Command?
How much does the Google Drive integration cost?
More cloud & storage apps people connect.
Same category as Google Drive, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Google Drive.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
