Can HumDay connect to Google On Demand Scanning?

Yes. HumDay reads Google On Demand Scanning's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 7 operations are documented.

Do I need to write code to automate Google On Demand Scanning?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google On Demand Scanning account.

What can HumDay do in Google On Demand Scanning?

4 of the 7 documented operations change something in Google On Demand Scanning, and 3 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google On Demand Scanning account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google On Demand Scanning is held behind that approval.

Automate Google On Demand Scanning

HumDay reads Google On Demand Scanning’s own published API description and derives 7 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Google On Demand Scanning is

A service to scan container images for vulnerabilities.

API host: ondemandscanning.googleapis.com

What HumDay can do in Google On Demand Scanning

4 documented operations change something in Google On Demand Scanning.

DELETEDeletes a long-running operation./v1beta1/{name}
POSTWaits until the specified long-running operation is done or reaches at most a specified timeout, returning the latest state./v1beta1/{name}:wait
POSTStarts asynchronous cancellation on a long-running operation./v1beta1/{name}:cancel
POSTInitiates an analysis of the provided packages./v1beta1/{parent}/scans:analyzePackages

What HumDay can read from Google On Demand Scanning

These are the operations a schedule or a trigger can watch.

GETGets the latest state of a long-running operation./v1beta1/{name}
GETLists operations that match the specified filter in the request./v1beta1/{name}/operations
GETLists vulnerabilities resulting from a successfully completed scan./v1beta1/{parent}/vulnerabilities

How automating Google On Demand Scanning works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Google On Demand Scanning account.
Grant access, then go live. You approve the specific Google On Demand Scanning operations it may use — and only those.