List Databases

biglake.list_databases
ActionGoogle Cloudconnection required

Calls Lakehouse GET /v1/projects/{projectsId}/locations/{locationsId}/catalogs/{catalogsId}/databases.

List all databases in a specified catalog.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Lakehouse
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
location, project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

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

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
location
Location / region (overrides connection).
stringNo———
catalog
Id of the catalog to act on, from biglake.list_catalogs — not its name.
stringYes———
page_size
The maximum number of databases to return. The service may return fewer than this value. If unspecified, at mo
numberNo50≥ 1—
page_token
A page token, received from a previous `ListDatabases` call. Provide this to retrieve the subsequent page. Whe
stringNo———

Example configuration

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

{
  "page_size": 50
}

Output

One shape.

result

FieldTypeExample
ok
boolean—
nextPageToken
string—
databases
array—
{
  "databases": [],
  "nextPageToken": "",
  "ok": false
}

See List Databases run in a workflow.

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