Can HumDay connect to Google Usage?

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

Do I need to write code to automate Google Usage?

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 Usage account.

What can HumDay do in Google Usage?

10 of the 16 documented operations change something in Google Usage, and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Usage

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

Enables services that service consumers want to use on Google Cloud Platform, lists the available or enabled services, or disables services that service consumers no longer use.

API host: serviceusage.googleapis.com

What HumDay can do in Google Usage

10 documented operations change something in Google Usage.

POSTCreates a consumer override./v1beta1/{parent}/consumerOverrides
DELETEDeletes a consumer override./v1beta1/{name}
PATCHUpdates a consumer override./v1beta1/{name}
POSTEnables a service so that it can be used with a project./v1beta1/{name}:enable
POSTCreates or updates multiple consumer overrides atomically, all on the same consumer, but on many different metrics or limits./v1beta1/{parent}/consumerQuotaMetrics:importConsumerOverrides
POSTDisables a service so that it can no longer be used with a project./v1beta1/{name}:disable
POSTGenerates service identity for service./v1beta1/{parent}:generateServiceIdentity
POSTEnables multiple services on a project./v1beta1/{parent}/services:batchEnable
POSTCreates an admin override./v1beta1/{parent}/adminOverrides
POSTCreates or updates multiple admin overrides atomically, all on the same consumer, but on many different metrics or limits./v1beta1/{parent}/consumerQuotaMetrics:importAdminOverrides

What HumDay can read from Google Usage

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

GETLists operations that match the specified filter in the request./v1beta1/operations
GETLists all services available to the specified project, and the current state of those services with respect to the project./v1beta1/{parent}/services
GETLists all consumer overrides on this limit./v1beta1/{parent}/consumerOverrides
GETRetrieves a summary of quota information for a specific quota limit./v1beta1/{name}
GETLists all admin overrides on this limit./v1beta1/{parent}/adminOverrides
GETRetrieves a summary of all quota information visible to the service consumer, organized by service metric./v1beta1/{parent}/consumerQuotaMetrics

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