Get Alert
cloud_monitoring.get_alert
ActionGoogle Cloudconnection required
Calls monitoring v3 GET /v3/projects/{projectsId}/alerts/{alertsId}.
Gets a single alert.
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
1 field, 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 |
|---|---|---|---|---|---|
alert Alert name or id. | string | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
closeTime | string | — |
log | object | — |
metadata | object | — |
metric | object | — |
name | string | — |
openTime | string | — |
policy | object | — |
resource | object | — |
state | string | — |
{
"closeTime": "",
"log": {},
"metadata": {},
"metric": {},
"name": "",
"openTime": "",
"policy": {},
"resource": {},
"state": ""
}See Get Alert 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.