Download Storage Object
supabase.storage_download
ActionDatabases & warehousesconnection required
Calls the Supabase API with the connection's credentials.
Download an object from a Storage bucket as a base64 file payload that an upload or parse node downstream can consume directly.
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
2 fields, 2 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 |
|---|---|---|---|---|---|
bucket The Storage bucket name. | string | Yes | — | — | invoices |
path Object key inside the bucket, including any folder prefix. | string | Yes | — | — | 2026/09/invoice-1001.pdf |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"bucket": "invoices",
"path": "2026/09/invoice-1001.pdf"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
file_content The file, base64-encoded. | string | — |
content_encoding | string | base64 |
filename | string | app-main.zip |
content_type | string | application/zip |
size Raw size in bytes (before base64). | number | — |
bucket The bucket the object came from. | string | — |
path The object key inside the bucket. | string | — |
{
"bucket": "",
"content_encoding": "base64",
"content_type": "application/zip",
"file_content": "",
"filename": "app-main.zip",
"path": "",
"size": 0
}Notes
- The object is held in memory and returned inline, so it is capped by MANTLE_BINARY_MAX_BYTES; sign a URL instead for anything larger.
See Download Storage Object 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.