Can HumDay connect to Google OS Config?

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

Do I need to write code to automate Google OS Config?

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 OS Config account.

What can HumDay do in Google OS Config?

9 of the 14 documented operations change something in Google OS Config, and 5 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google OS Config

HumDay reads Google OS Config’s own published API description and derives 14 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 OS Config is

OS management tools that can be used for patch management, patch compliance, and configuration management on VM instances.

API host: osconfig.googleapis.com

What HumDay can do in Google OS Config

9 documented operations change something in Google OS Config.

POSTCreate an OS Config guest policy./v1beta/{parent}/guestPolicies
POSTCreate an OS Config patch deployment./v1beta/{parent}/patchDeployments
DELETEDelete an OS Config patch deployment./v1beta/{name}
PATCHUpdate an OS Config patch deployment./v1beta/{name}
POSTChange state of patch deployment to "PAUSED"./v1beta/{name}:pause
POSTCancel a patch job. The patch job must be active. Canceled patch jobs cannot be restarted./v1beta/{name}:cancel
POSTChange state of patch deployment back to "ACTIVE"./v1beta/{name}:resume
POSTLookup the effective guest policy that applies to a VM instance./v1beta/{instance}:lookupEffectiveGuestPolicy
POSTPatch VM instances by creating and running a patch job./v1beta/{parent}/patchJobs:execute

What HumDay can read from Google OS Config

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

GETGet a list of patch jobs./v1beta/{parent}/patchJobs
GETGet a page of OS Config guest policies./v1beta/{parent}/guestPolicies
GETGet a list of instance details for a given patch job./v1beta/{parent}/instanceDetails
GETGet a page of OS Config patch deployments./v1beta/{parent}/patchDeployments
GETGet the patch job. This can be used to track the progress of an ongoing patch job or review the details of completed jobs./v1beta/{name}

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