ActionGoogle Cloud StorageUpdated June 2026

How do I upload to Google Cloud Storage?

Short answer: You can upload 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 Upload GCS Object action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Upload GCS Object in Google Cloud Storage — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Bucket
bucket
stringOptional
Object Name (path)
name
stringRequireduploads/file.png
File content (URL/base64/raw)
content
stringRequired
Content Type
contentType
stringOptional
Sample request
{
"bucket": "{{trigger.bucket}}",
"name": "uploads/file.png",
"content": "{{trigger.content}}",
"contentType": "{{trigger.contentType}}"
}
Returns
{
"name": "uploads/file.png",
"size": "12345",
"bucket": "my-bucket",
"mediaLink": "https://storage.googleapis.com/...",
"contentType": "image/png"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Upload GCS Object.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Upload GCS Object.

What does the Upload GCS Object action do in Google Cloud Storage?
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.
What inputs does Upload GCS Object require?
Required: Object Name (path), File content (URL/base64/raw). 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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Upload GCS Object support batch operations?
Yes. Run Upload GCS Object inside a Loop node to process arrays. TinyCommand handles Google Cloud Storage's rate limits automatically so you don't have to throttle manually.
More actions

Other Google Cloud Storage actions.

Action
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.
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.
Action
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.
Action
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 in Google Cloud Storage — start free