List Scan Runs
web_security_scanner.list_scan_runs
ActionGoogle Cloudconnection required
Calls Web Security Scanner GET /v1/projects/{projectsId}/scanConfigs/{scanConfigsId}/scanRuns.
Lists ScanRuns under a given ScanConfig, in descending order of ScanRun stop time.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Web Security Scanner
- 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 | — | — | — |
scan_config Scan config id. | string | Yes | — | — | — |
page_size The maximum number of ScanRuns to return, can be limited by server. If not specified or not positive, the impl | number | No | 50 | ≥ 1 | — |
page_token A token identifying a page of results to be returned. This should be a `next_page_token` value returned from a | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"page_size": 50
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
scanRuns | array | — |
nextPageToken | string | — |
{
"nextPageToken": "",
"ok": false,
"scanRuns": []
}Related Google Web Security Scanner nodes
See List Scan Runs run in a workflow.
In a technical demo we add the Google Web Security Scanner connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.