Can HumDay connect to Google Organization Policy?

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

Do I need to write code to automate Google Organization Policy?

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 Organization Policy account.

What can HumDay do in Google Organization Policy?

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

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

Automate Google Organization Policy

HumDay reads Google Organization Policy’s own published API description and derives 9 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 Organization Policy is

The Org Policy API allows users to configure governance rules on their GCP resources across the Cloud Resource Hierarchy.

API host: orgpolicy.googleapis.com

What HumDay can do in Google Organization Policy

4 documented operations change something in Google Organization Policy.

POSTCreates a policy. Returns a google.rpc.Status with google.rpc.Code.NOTFOUND if the constraint does not exist. Returns a google.rpc.Status with google.rpc.Code.ALREADYEXISTS if the…/v2/{parent}/policies
POSTCreates a custom constraint./v2/{parent}/customConstraints
DELETEDeletes a policy. Returns a google.rpc.Status with google.rpc.Code.NOTFOUND if the constraint or organization policy does not exist./v2/{name}
PATCHUpdates a policy. Returns a google.rpc.Status with google.rpc.Code.NOTFOUND if the constraint or the policy do not exist. Returns a google.rpc.Status with google.rpc.Code.ABORTED…/v2/{name}

What HumDay can read from Google Organization Policy

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

GETGets a policy on a resource./v2/{name}
GETGets the effective policy on a resource./v2/{name}:getEffectivePolicy
GETRetrieves all of the policies that exist on a particular resource./v2/{parent}/policies
GETLists constraints that could be applied on the specified resource./v2/{parent}/constraints
GETRetrieves all of the custom constraints that exist on a particular organization resource./v2/{parent}/customConstraints

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