Execute
cloud_workflows.execute
ActionGoogle Cloudconnection required
Calls Workflow Executions API v1 POST .../workflows/{w}/executions.
Start a Cloud Workflows execution with a JSON argument (no polling).
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Workflows
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, location
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
location Location (overrides connection). | string | No | us-central1 | — | — |
workflow Workflow name. | string | Yes | — | — | — |
argument Execution argument as JSON. | object | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"location": "us-central1"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
name | string | — |
execution_id | string | — |
state | string | — |
done | boolean | — |
{
"done": false,
"execution_id": "",
"name": "",
"ok": false,
"state": ""
}Related Google Cloud Workflows nodes
See Execute run in a workflow.
In a technical demo we add the Google Cloud Workflows connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.