List Entries
cloud_logging.list_entries
ActionGoogle Cloudconnection required
Calls POST /entries:list with resourceNames, filter, orderBy and pageSize.
Query Cloud Logging entries in a project with a filter.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Logging
- 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, none 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 | — | — | — |
filter Logging filter (e.g. severity>=ERROR). | string | No | — | — | — |
order_by Cloud Logging sort expression; blank keeps the order it returns them in. | string | No | timestamp desc | one of "timestamp desc", "timestamp asc" | — |
page_size Max entries to return. | number | No | 50 | ≥ 1 | — |
page_token Page token from a previous call. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"order_by": "timestamp desc",
"page_size": 50
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
entries | array | — |
count | number | — |
next_page_token | string | — |
{
"count": 0,
"entries": [],
"next_page_token": ""
}Related Google Cloud Logging nodes
Solutions with Google Cloud Logging
See List Entries run in a workflow.
In a technical demo we add the Google Cloud Logging connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.