Google Cloud Storage
Google Cloud Storage object actions
Google Cloud Storage on Tiny Command exposes the object-CRUD surface of GCS buckets. Five actions, no triggers (GCS object notifications go through Pub/Sub rather than direct webhooks — configure a Pub/Sub topic subscription via the Pub/Sub connector for event-driven workflows): List Objects (within a bucket, with optional prefix filter), Upload Object (from a URL, base64, or text content, with content-type and custom metadata), Get Object Metadata (size, content-type, generation, MD5, custom metadata; not the content itself), Delete Object, and Get Signed URL (Public Download) — generates a time-limited URL anyone can use to download the object without GCS auth, the standard pattern for "send file to customer" workflows that don't want to proxy the bytes through the workflow runtime. The connection uses a Google Cloud service-account key (JSON) with the relevant Storage role (Storage Object Viewer for reads, Storage Object Admin for writes). The service account must be granted access to the buckets the workflow touches — IAM scoped at the bucket level for least privilege.
Do anything Google Cloud Storage 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 |
|---|---|
| Delete GCS Object | Removes a specific object from a bucket. Irreversible. For cleanup workflows after processing or for "GDPR right-to-erasure → delete user-uploaded files" compliance patterns. |
| Get GCS Object Metadata | Returns size, content-type, generation, MD5, custom metadata for an object — without downloading the content bytes. Useful for inventory or "did this file exist?" pre-flight checks. |
| Get Signed URL (Public Download) | Generates a time-limited URL that anyone can use to download the object without GCS auth. For "email the customer their export file" workflows that don't want to proxy bytes through the workflow runtime. |
| List GCS Objects | Returns paginated objects in a bucket with optional prefix filter. Useful for batch processing or for inventorying bucket contents. |
| Upload GCS Object | Uploads an object from URL, base64, or text content with optional metadata and content-type. For files >32MB, the simple upload path caps out — use resumable uploads via HTTP action. |
Pre-built Google Cloud Storage workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every Google Cloud Storage event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn Google Cloud Storage 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 Cloud Storage once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Google Cloud Storage 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 Cloud Storage integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Google Cloud Storage to Tiny Command?
What Google Cloud Storage triggers does Tiny Command support?
What Google Cloud Storage actions can I run from a workflow?
Is the Google Cloud Storage integration real-time?
Do I need to write code to use Google Cloud Storage with Tiny Command?
How much does the Google Cloud Storage integration cost?
More other apps people connect.
Same category as Google Cloud Storage, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Google Cloud Storage.
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.
