Start Cluster
dataproc.start_cluster
ActionGoogle Cloudconnection required
Calls Dataproc POST /regions/{r}/clusters/{name}:start.
Start a stopped Dataproc cluster (long-running operation).
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Dataproc
- 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, 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 | — | — | — |
region GCP region (overrides connection). | string | No | — | — | — |
cluster_name Name of the cluster to act on, from dataproc.list_clusters. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
operation | string | — |
done | boolean | — |
{
"done": false,
"operation": ""
}Related Google Cloud Dataproc nodes
See Start Cluster run in a workflow.
In a technical demo we add the Google Cloud Dataproc connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.