List Engines

discovery_engine.list_engines
ActionGoogle Cloudconnection required

Calls Discovery Engine GET /v1/projects/{projectsId}/locations/{locationsId}/collections/{collectionsId}/engines.

Lists all the Engines associated with the project.

Connection

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

Configuration

6 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———
collection
Collection id.
stringYes———
filter
Optional. Filter by solution type. For example: solution_type=SOLUTION_TYPE_SEARCH
stringNo———
page_size
Optional. Not supported.
numberNo50≥ 1—
page_token
Optional. Not supported.
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—
engines
array—
nextPageToken
string—
{
  "engines": [],
  "nextPageToken": "",
  "ok": false
}

See List Engines run in a workflow.

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