Create Scan Config
web_security_scanner.create_scan_config
ActionGoogle Cloudconnection required
Calls websecurityscanner v1 POST /v1/projects/{projectsId}/scanConfigs.
Creates a new 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
1 field, 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 |
|---|---|---|---|---|---|
body The ScanConfig resource, as the API defines it. | object | Yes | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
authentication | object | — |
blacklistPatterns | array | — |
displayName | string | — |
exportToSecurityCommandCenter | string | — |
ignoreHttpStatusErrors | boolean | — |
latestRun | object | — |
managedScan | boolean | — |
maxQps | integer | — |
name | string | — |
riskLevel | string | — |
schedule | object | — |
startingUrls | array | — |
staticIpScan | boolean | — |
targetPlatforms | array | — |
userAgent | string | — |
{
"authentication": {},
"blacklistPatterns": [],
"displayName": "",
"exportToSecurityCommandCenter": "",
"ignoreHttpStatusErrors": false,
"latestRun": {},
"managedScan": false,
"maxQps": 0,
"name": "",
"riskLevel": "",
"schedule": {},
"startingUrls": [],
"staticIpScan": false,
"targetPlatforms": [],
"userAgent": ""
}Related Google Web Security Scanner nodes
See Create 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.