HumDay

Queries the contact center quota in Google Contact Center AI Platform

A documented Google Contact Center AI Platform 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

Queries the contact center quota, an aggregation over all the projects, that belongs to the billing account, which the input project belongs to.

  • GETReads data · projectscontactcenteraiplatform.googleapis.com/v1alpha1/{parent}:queryContactCenterQuota

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 Contact Center AI Platform 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 Contact Center AI Platform operations

All 9 Google Contact Center AI Platform operations

Questions

Can HumDay queries the contact center quota in Google Contact Center AI Platform?
Yes. This operation is published in Google Contact Center AI Platform'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 Contact Center AI Platform 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 Contact Center AI Platform.
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 Contact Center AI Platform account.

Where this came from

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