Launch Template
dataflow.launch_template
ActionGoogle Cloudconnection required
Calls Dataflow POST /locations/{l}/templates:launch?gcsPath=.
Launch a classic Dataflow template from a GCS path.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Dataflow
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, location
- Resolved by
- config.connection_id, else node.connection_id
Configuration
6 fields, 2 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 GCP location (overrides connection). | string | No | — | — | — |
gcs_path gs:// path of the template. | string | Yes | — | — | — |
job_name Name for the new job. | string | Yes | — | — | — |
parameters Template parameters as JSON object. | object | No | — | — | — |
environment RuntimeEnvironment JSON (tempLocation, ...). | object | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
job_id | string | — |
job_name | string | — |
state | string | — |
{
"job_id": "",
"job_name": "",
"state": ""
}Related Google Cloud Dataflow nodes
See Launch Template run in a workflow.
In a technical demo we add the Google Cloud Dataflow connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.