List Services

service_directory.list_services
ActionGoogle Cloudconnection required

Calls Service Directory GET /v1/projects/{projectsId}/locations/{locationsId}/namespaces/{namespacesId}/services.

Lists all services belonging to a namespace.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Service Directory
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———
namespace
Namespace id.
stringYes———
filter
Optional. The filter to list results by. General `filter` string syntax: ` ()` * `` can be `name` or `annotati
stringNo———
order_by
Optional. The order to list results by.
stringNo———
page_size
Optional. The maximum number of items to return.
numberNo50≥ 1—
page_token
Optional. The next_page_token value returned from a previous List request, if any.
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—
services
array—
nextPageToken
string—
{
  "nextPageToken": "",
  "ok": false,
  "services": []
}

See List Services run in a workflow.

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