Start Scan Config
web_security_scanner.start_scan_config
ActionGoogle Cloudconnection required
Calls Web Security Scanner POST /v1/projects/{projectsId}/scanConfigs/{scanConfigsId}:start.
Start a ScanRun according to the given ScanConfig.
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
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 | — | — | — |
scan_config Scan config id. | string | Yes | — | — | — |
body Request body (StartScanRunRequest) as JSON. | object | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
resultState | string | — |
hasVulnerabilities | boolean | — |
urlsTestedCount | string | — |
startTime | string | — |
urlsCrawledCount | string | — |
progressPercent | number | — |
{
"hasVulnerabilities": false,
"ok": false,
"progressPercent": 0,
"resultState": "",
"startTime": "",
"urlsCrawledCount": "",
"urlsTestedCount": ""
}Related Google Web Security Scanner nodes
See Start Scan Config 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.