Can HumDay connect to Google Cloud Workstations?

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

Do I need to write code to automate Google Cloud Workstations?

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

What can HumDay do in Google Cloud Workstations?

11 of the 19 documented operations change something in Google Cloud Workstations, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Cloud Workstations

HumDay reads Google Cloud Workstations’s own published API description and derives 19 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 Cloud Workstations

11 documented operations change something in Google Cloud Workstations.

POSTCreates a new workstation./v1beta/{parent}/workstations
POSTCreates a new workstation configuration./v1beta/{parent}/workstationConfigs
POSTCreates a new workstation cluster./v1beta/{parent}/workstationClusters
POSTStarts running a workstation so that users can connect to it./v1beta/{name}:start
POSTReturns a short-lived credential that can be used to send authenticated and authorized traffic to a workstation./v1beta/{workstation}:generateAccessToken
DELETEDeletes the specified workstation./v1beta/{name}
PATCHUpdates an existing workstation./v1beta/{name}
POSTStops running a workstation, reducing costs./v1beta/{name}:stop
POSTStarts asynchronous cancellation on a long-running operation./v1beta/{name}:cancel
POSTSets the access control policy on the specified resource./v1beta/{resource}:setIamPolicy
POSTReturns permissions that a caller has on the specified resource./v1beta/{resource}:testIamPermissions

What HumDay can read from Google Cloud Workstations

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

GETReturns the requested workstation./v1beta/{name}
GETGets the access control policy for a resource./v1beta/{resource}:getIamPolicy
GETLists operations that match the specified filter in the request./v1beta/{name}/operations
GETReturns all Workstations using the specified config./v1beta/{parent}/workstations
GETReturns all workstation configurations in the specified cluster./v1beta/{parent}/workstationConfigs
GETReturns all workstation clusters in the specified location./v1beta/{parent}/workstationClusters
GETReturns all workstation configurations in the specified cluster on which the caller has the "workstations.workstation.create" permission./v1beta/{parent}/workstationConfigs:listUsable
GETReturns all Workstations using the specified config on which the caller has the "workstations.workstations.use" permission./v1beta/{parent}/workstations:listUsable

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