Group Finding
security_command_center.group_finding
ActionGoogle Cloudconnection required
Calls Security Command Center POST /v1/projects/{projectsId}/sources/{sourcesId}/findings:group.
Group Finding…
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
3 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 | — | — | — |
source Id of the source to act on, from security_command_center.list_sources — not its name. | string | Yes | — | — | — |
body Request body (GroupFindingsRequest) as JSON. | object | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
nextPageToken | string | — |
groupByResults | array | — |
readTime | string | — |
totalSize | number | — |
{
"groupByResults": [],
"nextPageToken": "",
"ok": false,
"readTime": "",
"totalSize": 0
}Related Google Security Command Center nodes
See Group Finding 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.