Delete Engine

discovery_engine.delete_engine
ActionGoogle Cloudconnection required

Calls discoveryengine v1 DELETE /v1/projects/{projectsId}/locations/{locationsId}/collections/{collectionsId}/engines/{enginesId}.

Deletes an Engine.

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
project_id, location
Resolved by
config.connection_id, else node.connection_id

Configuration

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

FieldTypeRequiredDefaultConstraintsExample
location
Location or region; taken from the connection when unset.
stringNo———
collection
Collection name or id.
stringYes———
engine
Engine name or id.
stringYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
done
boolean—
error
object—
metadata
object—
name
string—
response
object—
{
  "done": false,
  "error": {},
  "metadata": {},
  "name": "",
  "response": {}
}

See Delete Engine 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.