Trigger DAG
cloud_composer.trigger_dag
ActionGoogle Cloudconnection required
Calls Composer POST /environments/{e}:executeAirflowCommand (dags trigger).
Trigger an Airflow DAG run via the Composer CLI endpoint.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Composer
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, location
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 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 | — | — | — |
environment Environment name. | string | Yes | — | — | — |
dag_id DAG id to trigger. | string | Yes | — | — | — |
conf DAG run conf as JSON object (--conf). | object | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
execution_id | string | — |
pod | string | — |
pod_namespace | string | — |
dag_id | string | — |
error | string | — |
{
"dag_id": "",
"error": "",
"execution_id": "",
"pod": "",
"pod_namespace": ""
}Related Google Cloud Composer nodes
See Trigger DAG run in a workflow.
In a technical demo we add the Google Cloud Composer connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.