In oprder to authenticate, you need to receive apiKey
from your Google cloud platform
account
The technical notes page gives some technical details about Google-translate component like changelog.
This component has no trigger functions. This means it will not be accessible to select as a first component during the integration flow design.
When specifying the language in a Configure input
section, use two or three letter codes for that. For example,
english -> en
russian -> ru
franch -> fr
-----
english -> eng
russian -> rus
franch -> fra
Such codes can be foud in a result of Retrieve supported languages
action execution
sourceLang
field is optional. Google will autodetect the source locale if not specified.
in/out metadata can be found at /lib/schemas/translatePhrase.{in/out}.json
in/out metadata can be found at /lib/schemas/detectLanguage.{in/out}.json
out metadata can be found at /lib/schemas/retrieveSupportedLanguages.out.json
in/out metadata can be found at /lib/schemas/translateObjectProperties.{in/out}.json
input message:
{
"sourceObject": {
"hello": "hello world",
"capital": "London is the capital of Great Britain"
},
"sourceLang": "en",
"targetLang": "de"
}
output message:
{
"hello": "Hallo Welt",
"capital": "London ist die Hauptstadt von Großbritannien"
}
in/out metadata can be found at /lib/schemas/translateObjectProperties.{in/out}.json
input message:
{
"sourceArray": [
{
"hello": "hello world",
"capital": "London is the capital of Great Britain"
},
{
"color": "red",
"mood": "great mood"
}
],
"sourceLang": "en",
"targetLang": "de"
}
output message:
{
"translatedArray": [
{
"capital": "London ist die Hauptstadt von Großbritannien",
"hello": "Hallo Welt"
},
{
"mood": "großartige Stimmung",
"color": "rot"
}
]
}
You need to create new or use existing GCP project
and enable Google Cloud Translation API
Click here to learn more about the elastic.io iPaaS