Webhook Trigger Locations
cloud_build.webhook_trigger_locations
ActionGoogle Cloudconnection required
Calls cloudbuild v1 POST /v1/projects/{projectsId}/locations/{locationsId}/triggers/{triggersId}:webhook.
ReceiveTriggerWebhook [Experimental] is called when the API receives a webhook request targeted at a specific trigger.
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
3 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 |
|---|---|---|---|---|---|
location Location or region; taken from the connection when unset. | string | No | — | — | — |
trigger Trigger name or id. | string | Yes | — | — | — |
body The HttpBody resource, as the API defines it. | object | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
{}See Webhook Trigger Locations 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.