ActionAWS S3Updated September 2026

How do I list objects in an S3 bucket?

Short answer: You can list objects in AWS S3 by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the AWS S3 List 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 Objects in AWS S3 — start free All 5 AWS S3 actions

List Objects in AWS S3 — 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 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.

Triggered by

Apps that pair well as the trigger for List Objects.

Any of these apps can fire this action as part of a workflow.

Google Sheets → AWS S3

2 Google Sheets triggers

HubSpot → AWS S3

18 HubSpot triggers

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 run history shows the failed step with its input and the error message AWS S3 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 Objects support batch operations?

Run List 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 AWS S3's rate limits.

More actions