List Events
error_reporting.list_events
ActionGoogle Cloudconnection required
Calls Error Reporting GET /projects/{p}/events?groupId=.
List individual error events for one error group.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Error Reporting
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 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 | — | — | — |
group_id Error group id. | string | Yes | — | — | — |
period Time range — Error Reporting accepts only the listed values. | string | No | PERIOD_1_DAY | one of "PERIOD_1_HOUR", "PERIOD_6_HOURS", "PERIOD_1_DAY", "PERIOD_1_WEEK", "PERIOD_30_DAYS" | — |
page_size Max events (1-1000). | number | No | 50 | ≥ 1 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"page_size": 50,
"period": "PERIOD_1_DAY"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
events | array | — |
count | number | — |
next_page_token | string | — |
{
"count": 0,
"events": [],
"next_page_token": ""
}Related Google Cloud Error Reporting nodes
See List Events run in a workflow.
In a technical demo we add the Google Cloud Error Reporting connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.