Can HumDay connect to Google Cloud TPU?

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

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

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

What can HumDay do in Google Cloud TPU?

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

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

Automate Google Cloud TPU

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

TPU API provides customers with access to Google TPU technology.

API host: tpu.googleapis.com

What HumDay can do in Google Cloud TPU

8 documented operations change something in Google Cloud TPU.

POSTCreates a node./v2/{parent}/nodes
DELETEDeletes a long-running operation./v2/{name}
PATCHUpdates the configurations of a node./v2/{name}
POSTStops a node. This operation is only available with single TPU nodes./v2/{name}:stop
POSTStarts a node./v2/{name}:start
POSTStarts asynchronous cancellation on a long-running operation./v2/{name}:cancel
POSTRetrieves the guest attributes for the node./v2/{name}:getGuestAttributes
POSTGenerates the Cloud TPU service identity for the project./v2/{parent}:generateServiceIdentity

What HumDay can read from Google Cloud TPU

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

GETGets a runtime version./v2/{name}
GETLists nodes./v2/{parent}/nodes
GETLists information about the supported locations for this service./v2/{name}/locations
GETLists operations that match the specified filter in the request./v2/{name}/operations
GETLists runtime versions supported by this API./v2/{parent}/runtimeVersions
GETLists accelerator types supported by this API./v2/{parent}/acceleratorTypes

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