List Objects: AWS S3 action

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 Name bucket	string	Required	Bucket Name
Prefix Filter prefix	string	Optional	Prefix Filter. Example: images/2026/
Max Results maxKeys	number	Optional	Max Results

Sample request

{
  "bucket": "{{trigger.bucket}}",
  "prefix": "e.g. images/2026/",
  "maxKeys": "{{trigger.maxKeys}}"
}

Returns

{
  "Name": "my-bucket",
  "Contents": [
    {
      "Key": "images/photo.jpg",
      "Size": 204800,
      "LastModified": "2026-04-01T10:00:00Z"
    }
  ]
}

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

FAQ

Questions about List Objects.

What does the List Objects action do in AWS S3?

Lists objects in an S3 bucket, optionally scoped by prefix (folder). Returns up to 1000 keys per page; paginate with ContinuationToken for large buckets.

What inputs does List Objects require?

Required: Bucket 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 AWS S3 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 Objects support batch operations?

Yes. Run List Objects inside a Loop node to process arrays. Tiny Command handles AWS S3's rate limits automatically so you don't have to throttle manually.

More actions