ActionGoogle Cloud StorageUpdated September 2026

How do I list objects in a GCS bucket?

Short answer: You can list gcs objects in Google Cloud Storage by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Google Cloud Storage List GCS Objects action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List GCS Objects in Google Cloud Storage — start free All 5 Google Cloud Storage actions

List GCS Objects 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	Optional	–
Prefix Filter prefix	string	Optional	–
Max Results maxResults	string	Optional	–

Sample request

{
  "bucket": "{{trigger.bucket}}",
  "prefix": "{{trigger.prefix}}",
  "maxResults": "{{trigger.maxResults}}"
}

Returns

{
  "items": [
    {
      "name": "file.png",
      "size": "12345",
      "mediaLink": "https://storage.googleapis.com/..."
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for List GCS Objects.

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 List GCS Objects.

What does the List GCS Objects action do in Google Cloud Storage?

Returns paginated objects in a bucket with optional prefix filter. Useful for batch processing or for inventorying bucket contents.

What inputs does List GCS Objects require?

List GCS Objects has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List GCS Objects support batch operations?

Run List GCS Objects 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