Automate Google Workload Manager
HumDay reads Google Workload Manager’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 HumDay can do in Google Workload Manager
5 documented operations change something in Google Workload Manager.
- POSTCreates a new Evaluation in a given project and location.
/v1/{parent}/evaluations - POSTCreates a new Execution in a given project and location.
/v1/{name}/executions:run - DELETEDeletes a long-running operation.
/v1/{name} - POSTStarts asynchronous cancellation on a long-running operation.
/v1/{name}:cancel - POSTWrite the data insights to workload manager data warehouse.
/v1/{location}/insights:writeInsight
What HumDay can read from Google Workload Manager
These are the operations a schedule or a trigger can watch.
- GETList the running result of a single Execution.
/v1/{parent}/results - GETList all scanned resources for a single Execution.
/v1/{parent}/scannedResources - GETGets the latest state of a long-running operation.
/v1/{name} - GETLists rules in a given project.
/v1/{parent}/rules - GETLists information about the supported locations for this service.
/v1/{name}/locations - GETLists operations that match the specified filter in the request.
/v1/{name}/operations - GETLists Executions in a given project and location.
/v1/{parent}/executions - GETLists Evaluations in a given project and location.
/v1/{parent}/evaluations
How automating Google Workload Manager 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 Workload Manager account.
- Grant access, then go live. You approve the specific Google Workload Manager operations it may use — and only those.
Automate Google Workload Manager 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 Workload Manager automation
- Can HumDay connect to Google Workload Manager?
- Yes. HumDay reads Google Workload Manager'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 Workload Manager?
- 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 Workload Manager account.
- What can HumDay do in Google Workload Manager?
- 5 of the 13 documented operations change something in Google Workload Manager, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Workload Manager 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 Workload Manager is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Workload Manager at workloadmanager.googleapis.com/$discovery/rest?version=v1. Descriptions are the provider’s own words, not ours. Last published 2023-04-21.