Automate Google Cloud Support
HumDay reads Google Cloud Support’s own published API description and derives 13 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 Cloud Support is
Manages Google Cloud technical support cases for Customer Care support offerings.
API host: cloudsupport.googleapis.com
What HumDay can do in Google Cloud Support
6 documented operations change something in Google Cloud Support.
- POSTAdd a new comment to the specified Case.
/v2beta/{parent}/comments - POSTCreate a new case and associate it with the given Cloud resource.
/v2beta/{parent}/cases - POSTCreate a file attachment on a case or Cloud resource.
/v2beta/{parent}/attachments - POSTEscalate a case. Escalating a case will initiate the Cloud Support escalation management process. This operation is only available to certain Customer Care tiers. Go to and look f…
/v2beta/{name}:escalate - PATCHUpdate the specified case.
/v2beta/{name} - POSTClose the specified case.
/v2beta/{name}:close
What HumDay can read from Google Cloud Support
These are the operations a schedule or a trigger can watch.
- GETSearch cases using the specified query.
/v2beta/cases:search - GETRetrieve valid classifications to be used when creating a support case.
/v2beta/caseClassifications:search - GETDownload a file attachment on a case.
/v2beta/{name}:download - GETRetrieve all Comments associated with the Case object.
/v2beta/{parent}/comments - GETRetrieve the specified case.
/v2beta/{name} - GETRetrieve all cases under the specified parent.
/v2beta/{parent}/cases - GETRetrieve all attachments associated with a support case.
/v2beta/{parent}/attachments
How automating Google Cloud Support 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 Cloud Support account.
- Grant access, then go live. You approve the specific Google Cloud Support operations it may use — and only those.
Automate Google Cloud Support with these
- Gmail79 operations
- Google+9 operations
- Google Abusive Experience Report2 operations
- Google Accelerated Mobile Pages (AMP) URL1 operations
- Google Access Approval7 operations
- Google Access Context Manager9 operations
- Google ACME DNS2 operations
- Google Ad Exchange Buyer38 operations
- Google Ad Exchange Buyer II50 operations
- Google Ad Experience Report2 operations
- Google Admin SDK122 operations
- Google AdMob7 operations
Categories
Questions about Google Cloud Support automation
- Can HumDay connect to Google Cloud Support?
- Yes. HumDay reads Google Cloud Support's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 13 operations are documented.
- Do I need to write code to automate Google Cloud Support?
- 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 Cloud Support account.
- What can HumDay do in Google Cloud Support?
- 6 of the 13 documented operations change something in Google Cloud Support, and 7 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Cloud Support 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 Cloud Support is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Cloud Support at cloudsupport.googleapis.com/$discovery/rest?version=v2beta. Descriptions are the provider’s own words, not ours. Last published 2023-04-21.