ActionGoogle Cloud StorageUpdated September 2026
How do I delete a Google Cloud Storage object?
Short answer: You can delete gcs object in Google Cloud Storage by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Google Cloud Storage Delete GCS Object action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Bucket bucket | string | Required | – |
Object Name object | string | Required | – |
Sample request
{"bucket": "{{trigger.bucket}}","object": "{{trigger.object}}"}
Returns
{}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Delete GCS Object.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Delete GCS Object.
What does the Delete GCS Object action do in Google Cloud Storage?
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.
What inputs does Delete GCS Object require?
Required: Bucket, Object Name. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Google Cloud Storage returns an error?
The run history shows the failed step with its input and the error message Google Cloud Storage returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Delete GCS Object support batch operations?
Run Delete GCS Object inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Google Cloud Storage's rate limits.
More actions
Other Google Cloud Storage actions.
Action
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.
ActionGet 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.
ActionList GCS Objects
Returns paginated objects in a bucket with optional prefix filter. Useful for batch processing or for inventorying bucket contents.
ActionUpload 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.