Data API базы: бакеты файлов
data_api_bucketsStorage buckets of a database: list and create — without a secret key.
Files must be enabled for the database. A private bucket opens nothing by
itself: reading and uploading are decided by storage policies (the
dashboard → Files → Policies, or SQL on storage.objects). Creating needs
the person's consent. Needs a token with the admin scope — the storage key
is issued only to it, even for listing.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | For create: bucket name, e.g. `screenshots`. | |
| action | No | `list` — the database's storage buckets; `create` — a new bucket. | list |
| public | No | For create: anyone with the link can download files. Default false — who reads and uploads is decided by storage policies. | |
| database | No | The database: name, slug or id. Without it — the organization's only database with the Data API enabled. | |
| confirmed | No | true — the person has already agreed in the chat after seeing what will change. A client with forms does not need it: the server asks the person itself. Never set it without the person's explicit consent. | |
| organization | No | Organization slug. Without it — the only one, or the personal one. | |
| max_size_bytes | No | For create: file size limit in bytes. | |
| allowed_mime_types | No | For create: allowed MIME types, e.g. ["image/jpeg", "image/png"]. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | ||
| buckets | No | ||
| changed | No | ||
| database | Yes | ||
| next_action | Yes | ||
| organization | Yes |