Wait Operation Locations

cloud_run.wait_operation_locations
ActionGoogle Cloudconnection required

Calls run v2 POST /v2/projects/{projectsId}/locations/{locationsId}/operations/{operationsId}:wait.

Waits until the specified long-running operation is done or reaches at most a specified timeout, returning the latest state.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Cloud Run
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id, region
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———
operation
Operation name or id.
stringYes———
body
The GoogleLongrunningWaitOperationRequest resource, as the API defines it.
objectYes———

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 Wait Operation Locations run in a workflow.

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