Can HumDay connect to Google Cloud Shell?

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

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

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

What can HumDay do in Google Cloud Shell?

6 of the 7 documented operations change something in Google Cloud Shell, and 1 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Cloud Shell

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

Allows users to start, configure, and connect to interactive shell sessions running in the cloud.

API host: cloudshell.googleapis.com

What HumDay can do in Google Cloud Shell

6 documented operations change something in Google Cloud Shell.

POSTAdds a public SSH key to an environment, allowing clients with the corresponding private key to connect to that environment via SSH./v1/{environment}:addPublicKey
POSTStarts an existing environment, allowing clients to connect to it./v1/{name}:start
POSTRemoves a public SSH key from an environment./v1/{environment}:removePublicKey
DELETEDeletes a long-running operation./v1/{name}
POSTStarts asynchronous cancellation on a long-running operation./v1/{name}:cancel
POSTSends OAuth credentials to a running environment on behalf of a user./v1/{name}:authorize

What HumDay can read from Google Cloud Shell

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

GETGets an environment. Returns NOTFOUND if the environment does not exist./v1/{name}

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