Search
.
PubNub Integration

Google Translation API

Contact Sales
Or Try it Now
Bots & AI

Bots & AI

Chat & Social

Chat & Social

External APIs

External APIs

In-app chat

In-app chat

Multiuser Spaces

Multiuser Spaces

Last Updated:

2020/05/08

Author:

PubNub, Inc.

APISign-upDocumentation
MIT/OPEN SOURCE License

ML-based language translation

Dynamically translate between languages using Google machine learning. Google Translation enables fast, dynamic translation tailored to your content needs.Supports more than one hundred languages, from Afrikaans to Zulu.

Google Translation API

Setup:

  1. Sign-up for a Google Cloud account and setup the Natural Language API.

  2. Sign-up for a PubNub account, if you don't have one already.

  3. Import the Integration Block into your PubNub account. You can choose to add this to an existing application or create a new one.

  4. Configure the Integration Block module code, connecting it to your Google Cloud account:

    1. Create a Secret in PubNub Vault, named GOOGLE_TRANSLATION_SERVICES_APIKEY, with value equal to your Google API Key for this service, retrieved as part of step 1 above.

  5. Start the Integration Block module.

  6. Try a test message (you can click on Publish to do this).

Walkthrough:

This Integration Block is setup to listen to a specific PubNub channel (CHANNEL-to-translate-Google) but you can configure it to listen to all channels or a subset, using wildcards, e.g. chat.*. Thus, you can add machine learning-generated translation capabilities even in private chats and other secure communication channels. The Integration Block is flexible in that it can be used both as part of a PubNub messaging flow, i.e. as part of publishing data, as well as accessed separately through a REST endpoint. Additionally, customization of capabilities can be done through publish message metadata or REST query parameters. In publish metadata, the customization properties are set as part of a JSON object specific for the function named google-translate-v2.

  1. TEXT_LOCATION_ID: json dot notation for locating the text field in the message payload.

  2. INPUT_TEXT_MODEL: direct configuration of the Google Translation API property

  3. INPUT_TEXT_TYPE: direct configuration of the Google Translation API property

  4. INPUT_TEXT_LANGUAGE: direct configuration of the Google Translation API property; this is the language of the input text

  5. INPUT_TARGET_LANGUAGE: direct configuration of the Google Translation API property; this is the target language into which the input text should be translated

  6. INPUT_TEXT_ENCODING_TYPE: direct configuration of the Google Natural Language API property

  7. OUTPUT_LOCATION_ID: json dot notation for locating the output data in the final message payload. Specify meta if you want the output data to be part of the metadata property of the message payload.

Input

Publish message containing message body to input channel. Input Channel: CHANNEL-to-translate-Google You can change this channel in the PubNub Administration Portal, using the Block's Function editor.

{ "text": "This is Awesome!"}

Output

The response from Google Translate API is included in the payload, or in the meta property of the published message. 

{
	"text": "This is Awesome!",
	"translations": {
		"google": {
			"data": {
				"translations": [{
					"translatedText": "¡Esto es asombroso!",
					"model": "nmt"
				}]
			}
		}
	}
}

Feedback & Support

Need help? Contact PubNub Support.

Talk to an expert

Contact Sales