ActionGoogle Cloud StorageUpdated May 2026

How do I upload to Google Cloud Storage?

Short answer: Drop the "Google Cloud Storage → Upload GCS Object" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 5 Google Cloud Storage actions

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	Optional	—
Object Name (path) name	string	Required	uploads/file.png
File content (URL/base64/raw) content	string	Required	—
Content Type contentType	string	Optional	—

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.

Gmail → Google Cloud Storage

1 Gmail triggers

Slack → Google Cloud Storage

13 Slack triggers

Google Sheets → Google Cloud Storage

2 Google Sheets triggers

HubSpot → Google Cloud Storage

18 HubSpot triggers

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. Tiny Command handles Google Cloud Storage's rate limits automatically so you don't have to throttle manually.

More actions