Google Translate Connector

Google Translate Connector

Integrating Tulip with Google Translate API

Introduction

Google Translate API allows the users to get supported languages and translates to the targeted language with the right access set to their google accounts. The goal of this connector is to integrate with Google Cloud Translate V3 Api with Tulip using HTTP Connectors & provide customers with an out-of-box connector that can be imported into their instance.

Purpose

We are going to highlight different HTTP connector functions that can be built by doing HTTP calls to Google Cloud Translator V3 API endpoints to interact with the Google Cloud Translator to try out various translating actions on the cloud translator that could be leveraged for various use cases.

API Doc

1. Google Cloud Translator

Pre-Requisites

1. Create an account on Google's cloud Console & configure the OAuth 2.0 credentials. More information can be found in Google's API docs.
2. Activate the Google Cloud Translator API in the Google API Console.

Tulip Connection Details

The following information would need to be configured on Tulip's connectors.

1. Running On: Cloud Connector Host
2. Host: translation.googleapis.com
3. Port: 443
4. TLS: Yes
5. Authentication: OAuth2.0(Admin/Operator)
6. Following are the scopes needed:

• https://www.googleapis.com/auth/cloud-platform
• https://www.googleapis.com/auth/cloud-translation

Connector Functions

Translate Text from Source to Target Language

Purpose

This connector will translate the text from the source language to the target language.

Endpoint

HTTP POST call to the endpoint https://translation.googleapis.com:443/language/translate/v2

Required Input

The following are the parameters that are sent as the Request Body

1. Target Language- Target Language to translate
2. Text - The Text to Translate

Required Output Extractor

1. Translated Text: The Translated text from source to the target language.
2. Source Language: The Source Language
3. Additional parameters that are returned with the response can be included as part of the output parameters