How does OCNORA authenticate with Google On-Demand Scanning?

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 On-Demand Scanning?

2 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the Google On-Demand Scanning operation I need is not listed?

Where Google On-Demand Scanning 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 On-Demand Scanning?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Google On-Demand Scanning 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.

Google On-Demand Scanning

Google CloudOAuth 2.0Connection test available

A service to scan container images for vulnerabilities (Google OAuth2).

OCNORA ships 2 typed Google On-Demand Scanning 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.

Ask about Google On-Demand Scanning Google On-Demand Scanning API docs ↗

Before you connect Google On-Demand Scanning

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 On-Demand Scanning

Operations, grouped by what they do to your data.

Read and search 1

List Vulnerabilities

Other operations 1

Analyze Packages

A sample Google On-Demand Scanning workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google On-Demand Scanning trigger is needed.
2
List Vulnerabilitieson_demand_scanning.list_vulnerabilities
Lists vulnerabilities resulting from a successfully completed scan.
3
Analyze Packageson_demand_scanning.analyze_packages
Initiates an analysis of the provided packages.

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 2