Google Web Security Scanner
Scans your Compute and App Engine apps for common web vulnerabilities (Google OAuth2).
OCNORA ships 8 typed Google Web Security Scanner operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Web Security Scanner
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Web Security Scanner
Operations, grouped by what they do to your data.
Create and send 2
Read and search 4
Update 1
Delete and cancel 1
A sample Google Web Security Scanner workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Web Security Scanner trigger is needed.
- 2Get Scan Configweb_security_scanner.get_scan_configGets a ScanConfig.
- 3Create Scan Configweb_security_scanner.create_scan_configCreates a new ScanConfig.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 8
- Create Scan ConfigCreates a new ScanConfig.web_security_scanner.create_scan_config
- Delete Scan ConfigDeletes an existing ScanConfig and its child resources.web_security_scanner.delete_scan_config
- Get Scan ConfigGets a ScanConfig.web_security_scanner.get_scan_config
- Get Scan RunGets a ScanRun.web_security_scanner.get_scan_run
- List Scan ConfigsLists ScanConfigs under a given project.web_security_scanner.list_scan_configs
- List Scan RunsLists ScanRuns under a given ScanConfig, in descending order of ScanRun stop time.web_security_scanner.list_scan_runs
- Start Scan ConfigStart a ScanRun according to the given ScanConfig.web_security_scanner.start_scan_config
- Update Scan ConfigUpdates a ScanConfig.web_security_scanner.update_scan_config
Google Web Security Scanner questions
- How does OCNORA authenticate with Google Web Security Scanner?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Web Security Scanner?
- 8 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Web Security Scanner operation I need is not listed?
- Where Google Web Security Scanner has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Web Security Scanner?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Web Security Scanner calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Web Security Scanner workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.