List Objects
s3.list_objects
ActionFiles & storageconnection required
Calls the S3 ListObjectsV2 API with a SigV4-signed request.
List objects in an S3 bucket, optionally filtered by prefix.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Amazon S3
- Secret shape
- {"access_key_id", "secret_access_key"}
- Config it needs
- region, bucket
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
prefix Key prefix filter. Supports {{ }}. | string | No | — | — | — |
max_keys Max objects (1-1000). | number | No | 100 | ≥ 1 | — |
next_token Continues a previous run of this node, using that run's next_token output. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"max_keys": 100
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
objects | array | — |
count | number | — |
next_token Cursor for the next page; empty when there are no further pages. S3 caps a page at 1,000 keys however large max_keys is. | string | — |
{
"count": 0,
"next_token": "",
"objects": []
}Related Amazon S3 nodes
Solutions with Amazon S3
See List Objects run in a workflow.
In a technical demo we add the Amazon S3 connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.