List Findings
guardduty.list_findings
ActionAmazon Web Servicesconnection required
Calls the AWS guardduty API (SigV4).
List finding ids for a detector.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Amazon GuardDuty
- Secret shape
- {"access_key_id", "secret_access_key"}
- Config it needs
- region
- 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 |
|---|---|---|---|---|---|
region AWS region (overrides the connection). | string | No | — | — | — |
detector_id Id of the detector to act on, from guardduty.list_detectors — not its name. | string | Yes | — | — | — |
max_results Max findings (default 25). | number | No | — | ≥ 1 | — |
next_token Continue a previous run of this node from where it stopped: the next_token value that run emitted. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
finding_ids | array | — |
count | number | — |
next_token Cursor for the next page; empty when there are no further pages. | string | — |
{
"count": 0,
"finding_ids": [],
"next_token": ""
}Related Amazon GuardDuty nodes
See List Findings run in a workflow.
In a technical demo we add the Amazon GuardDuty connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.