Can HumDay connect to Google Chrome Policy?

Yes. HumDay reads Google Chrome Policy'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 Chrome 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 Chrome Policy account.

What can HumDay do in Google Chrome Policy?

12 of the 14 documented operations change something in Google Chrome Policy, and 2 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Chrome Policy

HumDay reads Google Chrome Policy’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 Chrome Policy is

The Chrome Policy API is a suite of services that allows Chrome administrators to control the policies applied to their managed Chrome OS devices and Chrome browsers.

API host: chromepolicy.googleapis.com

What HumDay can do in Google Chrome Policy

12 documented operations change something in Google Chrome Policy.

POSTGets the resolved policy values for a list of policies that match a search query./v1/{customer}/policies:resolve
POSTCreates an enterprise file from the content provided by user./v1/{customer}/policies/files:uploadPolicyFile
POSTDefine a new network./v1/{customer}/policies/networks:defineNetwork
POSTCreates a certificate at a specified OU for a customer./v1/{customer}/policies/networks:defineCertificate
POSTDelete multiple policy values that are applied to a specific group./v1/{customer}/policies/groups:batchDelete
POSTModify multiple policy values that are applied to a specific group./v1/{customer}/policies/groups:batchModify
POSTModify multiple policy values that are applied to a specific org unit./v1/{customer}/policies/orgunits:batchModify
POSTModify multiple policy values that are applied to a specific org unit so that they now inherit the value from a parent (if applicable)./v1/{customer}/policies/orgunits:batchInherit
POSTRemove an existing network by guid./v1/{customer}/policies/networks:removeNetwork
POSTRemove an existing certificate by guid./v1/{customer}/policies/networks:removeCertificate
POSTRetrieve a group priority ordering for an app./v1/{customer}/policies/groups:listGroupPriorityOrdering
POSTUpdate a group priority ordering for an app./v1/{customer}/policies/groups:updateGroupPriorityOrdering

What HumDay can read from Google Chrome Policy

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

GETGets a list of policy schemas that match a specified filter value for a given customer./v1/{parent}/policySchemas
GETGet a specific policy schema for a customer by its resource name./v1/{name}

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