HumDay

Get a specific policy schema for a customer by its resource name

A documented Google Chrome Policy operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.

Automate this

What this operation does

Get a specific policy schema for a customer by its resource name.

  • GETReads data · customerschromepolicy.googleapis.com/v1/{name}

How HumDay uses it

  1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
  2. The contract names it. Before anything is built, you see exactly which Google Chrome Policy operations the program may use, and this is one of them.
  3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other Google Chrome Policy operations

All 14 Google Chrome Policy operations

Questions

Can HumDay get a specific policy schema for a customer by its resource name in Google Chrome Policy?
Yes. This operation is published in Google Chrome Policy's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
Does this change anything in my Google Chrome Policy account?
No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Google Chrome Policy.
Do I need to write code?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google Chrome Policy account.

Where this came from

Read from a published API description for Google Chrome Policy at chromepolicy.googleapis.com/$discovery/rest?version=v1. The description above is the provider’s own wording, not ours. Last published 2023-04-21.