ActionGoogle Cloud StorageUpdated September 2026

How do I get GCS object metadata?

Short answer: You can get gcs object metadata in Google Cloud Storage by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Google Cloud Storage Get GCS Object Metadata 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.

Get GCS Object Metadata in Google Cloud Storage — start free All 5 Google Cloud Storage actions

Get GCS Object Metadata 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.

Field	Type	Required	Description
Bucket bucket	string	Required	–
Object Name object	string	Required	–

Sample request

{
  "bucket": "{{trigger.bucket}}",
  "object": "{{trigger.object}}"
}

Returns

{
  "name": "file.png",
  "size": "12345",
  "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 Get GCS Object Metadata.

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 Get GCS Object Metadata.

What does the Get GCS Object Metadata action do in Google Cloud Storage?

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.

What inputs does Get GCS Object Metadata 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 Get GCS Object Metadata support batch operations?

Run Get GCS Object Metadata 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