Run Trigger
cloud_build.run_trigger
ActionGoogle Cloudconnection required
Calls Cloud Build API v1 POST /projects/{p}/triggers/{id}:run.
Run a Cloud Build trigger on a branch, tag or commit; returns the operation.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Build
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 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 | — | — | — |
trigger_id Trigger id or name. | string | Yes | — | — | — |
branch Branch name (source.branchName). | string | No | — | — | — |
tag Tag name (source.tagName). | string | No | — | — | — |
commit_sha Commit SHA (source.commitSha). | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
operation | string | — |
done | boolean | — |
build_id | string | — |
status | string | — |
log_url | string | — |
{
"build_id": "",
"done": false,
"log_url": "",
"ok": false,
"operation": "",
"status": ""
}See Run Trigger run in a workflow.
In a technical demo we add the Google Cloud Build connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.