List Zones

dataplex.list_zones
ActionGoogle Cloudconnection required

Calls Cloud Dataplex GET /v1/projects/{projectsId}/locations/{locationsId}/lakes/{lakesId}/zones.

Lists zone resources in a lake.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Cloud Dataplex
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
location, project_id
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
project_id
GCP project id (overrides connection).
stringNo———
location
Location / region (overrides connection).
stringNo———
lake
Id of the lake to act on, from dataplex.list_lakes — not its name.
stringYes———
filter
Optional. Filter request.
stringNo———
order_by
Optional. Order by fields for the result.
stringNo———
page_size
Optional. Maximum number of zones to return. The service may return fewer than this value.
numberNo50≥ 1—
page_token
Optional. Page token received from a previous ListZones call. Provide this to retrieve the subsequent page. Wh
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—
zones
array—
nextPageToken
string—
{
  "nextPageToken": "",
  "ok": false,
  "zones": []
}

See List Zones run in a workflow.

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