Update Alert Policy
cloud_monitoring.update_alert_policy
ActionGoogle Cloudconnection required
Calls monitoring v3 PATCH /v3/projects/{projectsId}/alertPolicies/{alertPoliciesId}.
Updates an alerting policy.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Monitoring
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 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 |
|---|---|---|---|---|---|
alert_policy Alert policy name or id. | string | Yes | — | — | — |
body The AlertPolicy resource, as the API defines it. | object | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
alertStrategy | object | — |
combiner | string | — |
conditions | array | — |
creationRecord | object | — |
displayName | string | — |
documentation | object | — |
enabled | boolean | — |
mutationRecord | object | — |
name | string | — |
notificationChannels | array | — |
severity | string | — |
userLabels | object | — |
validity | object | — |
{
"alertStrategy": {},
"combiner": "",
"conditions": [],
"creationRecord": {},
"displayName": "",
"documentation": {},
"enabled": false,
"mutationRecord": {},
"name": "",
"notificationChannels": [],
"severity": "",
"userLabels": {},
"validity": {}
}See Update Alert Policy run in a workflow.
In a technical demo we add the Google Cloud Monitoring connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.