How to list gcs objects in Google Cloud Storage

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.

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

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