Can HumDay connect to Google Cloud Translation?

Yes. HumDay reads Google Cloud Translation'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 Translation?

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

What can HumDay do in Google Cloud Translation?

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

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

Automate Google Cloud Translation

HumDay reads Google Cloud Translation’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 Translation is

Integrates text translation into your website or application.

API host: translation.googleapis.com

What HumDay can do in Google Cloud Translation

9 documented operations change something in Google Cloud Translation.

POSTTranslates a large volume of document in asynchronous batch mode./v3beta1/{parent}:batchTranslateDocument
POSTCreates a glossary and returns the long-running operation./v3beta1/{parent}/glossaries
DELETEDeletes a long-running operation./v3beta1/{name}
POSTWaits until the specified long-running operation is done or reaches at most a specified timeout, returning the latest state./v3beta1/{name}:wait
POSTStarts asynchronous cancellation on a long-running operation./v3beta1/{name}:cancel
POSTTranslates input text and returns translated text./v3beta1/{parent}:translateText
POSTDetects the language of text within a request./v3beta1/{parent}:detectLanguage
POSTTranslates documents in synchronous mode./v3beta1/{parent}:translateDocument
POSTTranslates a large volume of text in asynchronous batch mode./v3beta1/{parent}:batchTranslateText

What HumDay can read from Google Cloud Translation

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

GETReturns a list of supported languages for translation./v3beta1/{parent}/supportedLanguages
GETGets the latest state of a long-running operation./v3beta1/{name}
GETLists information about the supported locations for this service./v3beta1/{name}/locations
GETLists operations that match the specified filter in the request./v3beta1/{name}/operations
GETLists glossaries in a project./v3beta1/{parent}/glossaries

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