List Findings

security_command_center.list_findings
ActionGoogle Cloudconnection required

Calls Security Command Center GET /v1/projects/{projectsId}/sources/{sourcesId}/findings.

List Findings…

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Security Command Center
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

6 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
source
Id of the source to act on, from security_command_center.list_sources — not its name.
stringYes———
filter
Security Command Center filter expression; blank matches everything.
stringNo———
order_by
Security Command Center sort expression; blank keeps the order it returns them in.
stringNo———
page_size
Page size id.
numberNo50≥ 1—
page_token
Page token id.
stringNo———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "page_size": 50
}

Output

One shape.

result

FieldTypeExample
ok
boolean—
listFindingsResults
array—
totalSize
number—
readTime
string—
nextPageToken
string—
{
  "listFindingsResults": [],
  "nextPageToken": "",
  "ok": false,
  "readTime": "",
  "totalSize": 0
}

Related Google Security Command Center nodes

See List Findings run in a workflow.

In a technical demo we add the Google Security Command Center connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.