List Storage Objects

supabase.storage_list
ActionDatabases & warehousesconnection required

Calls the Supabase API with the connection's credentials.

List one page of objects in a Storage bucket, optionally under a folder prefix and filtered by a search term.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Supabase
Secret shape
the project API key, or {"api_key": "…"} / {"service_role_key": "…"}
Config it needs
base_url, schema
Resolved by
config.connection_id, else node.connection_id

Configuration

7 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
bucket
The Storage bucket name.
stringYes——invoices
prefix
Folder prefix to list under. Leave blank for the bucket root.
stringNo——2026/09
limit
Maximum objects to return in this page.
numberNo100≥ 1—
offset
Objects to skip before returning any, for paging.
numberNo—≥ 0—
sort_column
Column the API sorts the page by.
stringNonameone of "name", "updated_at", "created_at", "last_accessed_at"—
sort_order
Sort direction for the chosen column.
stringNoascone of "asc", "desc"—
search
Only return objects whose name contains this text.
stringNo———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "bucket": "invoices",
  "limit": 100,
  "prefix": "2026/09",
  "sort_column": "name",
  "sort_order": "asc"
}

Output

One shape.

result

FieldTypeExample
bucket
The bucket that was listed.
string—
prefix
The folder prefix that was listed.
string—
items
The objects, each with name, id, timestamps, metadata.
array—
count
How many objects this page returned.
number—
{
  "bucket": "",
  "count": 0,
  "items": [],
  "prefix": ""
}

See List Storage Objects run in a workflow.

In a technical demo we add the Supabase connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.