HumDay

Generates service identity for service in Google Usage

A documented Google Usage operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.

Automate this

What this operation does

Generates service identity for service.

  • POSTChanges data · servicesserviceusage.googleapis.com/v1beta1/{parent}:generateServiceIdentity

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 Usage operations the program may use, and this is one of them.
  3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Google Usage operations

All 16 Google Usage operations

Questions

Can HumDay generates service identity for service in Google Usage?
Yes. This operation is published in Google Usage's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
Will this change my Google Usage data?
Yes — this is a POST operation, so it changes something in Google Usage. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
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 Usage account.

Where this came from

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