Can HumDay connect to Google Assured Workloads?

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

Do I need to write code to automate Google Assured Workloads?

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 Assured Workloads account.

What can HumDay do in Google Assured Workloads?

5 of the 11 documented operations change something in Google Assured Workloads, and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Assured Workloads 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 Assured Workloads is held behind that approval.

Automate Google Assured Workloads

HumDay reads Google Assured Workloads’s own published API description and derives 11 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 HumDay can do in Google Assured Workloads

5 documented operations change something in Google Assured Workloads.

POSTRestrict the list of resources allowed in the Workload environment./v1beta1/{name}:restrictAllowedResources
POSTCreates Assured Workload./v1beta1/{parent}/workloads
DELETEDeletes the workload. Make sure that workload's direct children are already in a deleted state, otherwise the request will fail with a FAILEDPRECONDITION error. In addition to ass…/v1beta1/{name}
PATCHUpdates an existing workload./v1beta1/{name}
POSTAcknowledges an existing violation./v1beta1/{name}:acknowledge

What HumDay can read from Google Assured Workloads

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

GETRetrieves Assured Workload Violation based on ID./v1beta1/{name}
GETAnalyzes a hypothetical move of a source project or project-based workload to a target (destination) folder-based workload./v1beta1/{source}/{target}:analyzeWorkloadMove
GETAnalyzes a hypothetical move of a source project or project-based workload to a target (destination) folder-based workload./v1beta1/{project}/{target}:analyzeWorkloadMove
GETLists operations that match the specified filter in the request./v1beta1/{name}/operations
GETLists Assured Workloads under a CRM Node./v1beta1/{parent}/workloads
GETLists the Violations in the AssuredWorkload Environment./v1beta1/{parent}/violations

How automating Google Assured Workloads 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 Assured Workloads account.
Grant access, then go live. You approve the specific Google Assured Workloads operations it may use — and only those.