Remove Storage Objects
supabase.storage_remove
ActionDatabases & warehousesconnection required
Calls the Supabase API with the connection's credentials.
Permanently delete one or more objects from a Storage bucket and report which ones the API removed.
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 |
paths Object keys to delete, as a list of strings (a comma-separated string is also accepted, e.g. a.pdf, b.pdf). Keys are exact object paths, not wildcards. At least one key is required. | array | Yes | — | ≥ 1 characters; array of string | ["2026/09/invoice-1001.pdf"] |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"bucket": "invoices",
"paths": [
"2026/09/invoice-1001.pdf"
]
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
bucket The bucket the objects were removed from. | string | — |
requested The object keys that were asked for. | array | — |
items The object records the API reported as removed. | array | — |
count How many objects were actually removed. | number | — |
{
"bucket": "",
"count": 0,
"items": [],
"requested": []
}See Remove 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.