Setting up Translation System with Contentstack Webhooks, Memsource, and AWS Lambda

Memsource is a powerful Computer-assisted Translation (CAT) tool for translating general documents. This cloud-based platform allows businesses to process and translate hundreds of languages in different formats.

Memsource can be integrated with other systems and in this document, we will create a translation system using Contentstack Webhooks, Memsource, and AWS Lambda.

Additional Resource: Translation systems can also be set up using Contentstack Workflows and AWS Translate, to know more, read our guide on how to Set up a Translation System with Contentstack Webhooks and Workflows, AWS Lambda, and AWS Translate.

A brief overview of the process: When the workflow stage of entry changes to Send to Translation a webhook is triggered. Memsource will translate the content of the entry and once the translation is done, AWS Lambda will change the workflow stage to Review.

Here are the steps required to set up this translation system:

1. Set up the Essentials
2. Set up Workflows for Translation
3. Create a Memsource account
4. Set up Lambda function for translation
5. Trigger a webhook to initiate translation
   

Prerequisites

• Working knowledge of AWS API Gateways
• Access to the AWS environments such as AWS Lambda, AWS API Gateway, and AWS IAM
• Contentstack account
• Memsource account

1. Set up the Essentials

   First, create a stack, and add a content type (in our example it is “Memsource”),and add entries to it.

   Note: Ensure the field UID (body, multi_line, etc) in your code that you want to translate should match with the ones specified in the content type. In our example, it's title and body.

   Next, create languages (locales) in your content type (Memsource). In our example, we have added two languages:

   • English [en-us] which is the source language
   • Japanese [ja] is another language which will be our target language

   Note: Ensure that the languages you add are supported by Memsource. Also, ensure that you have localized the Japanese (ja) locale else the entry in your Japanese locale will not be translated. 

   Once you have these configured, then you're ready to begin the integration process for translation.

2. Set up Workflows for Translation

   To set up workflows for the translation process, log in to your Contentstack account and perform the following steps:

   1. Click the “Settings” icon (press “S”) on the left navigation panel and click on Workflows (press “alt + F” for Windows OS, and “option + F” for Mac OS to access workflows). 
   2. Click on + New Workflow.
   3. Add three stages (for example, Draft, Sent to Translation, and Review).
   
   

   Read more on how to set up workflows.

   Once the editor changes the workflow stage to Send to Translation, the webhook will be triggered and call the AWS Lambda function. The Lambda function will get the content translated from Memsource and will change the workflow stage to Review.

   We will need the workflow stage UID which we will enter when we set up our Lambda Function. This UID will instruct Lambda to change the workflow stage when the content is translated to Review.

   So proceed as follows to get the Review stage UID:

   1. Once you have created the workflow, it will show up like this:
      
      
      
      
   2. Open Postman or any other API collaboration & development platform and make a GET request on any of the following URL. Enter the Workflow ID (highlighted above) at the end of the URL:
      https://api.contentstack.io/v3/workflows/{YOUR WORKFLOW UID} 
      

      Note: For Europe region, the baseURL should be changed to https://eu-api.contentstack.com from https://api.contentstack.io. Similarly, for Azure NA region, change it to https://azure-na-api.contentstack.com

      You will get the following response:
      

   Tip: Make note of the UID highlighted in the above screenshot. We will need this in Step 4 when we set up our Environment Variable in the Lambda function.

3. Create a Memsource Account

   Memsource will translate the content into the target language. So create an account in Memsource by following the below steps:

   1. Sign up with Memsource.
   2. You can choose from the different plans they offer. For now, click on Free Trial at the top right side of the screen.
      
      

      Note: Avoid selecting the personal plan as it doesn't provide any arrangement for making API calls.
      

   3. On the Sign Up page, keep the settings as shown in the screenshot below and click on Sign Up with Email:
      
      
      
      
   4. On the next screen, enter your email, username, and password and click on Sign Up.

   With this, we have created an account in Memsource. Let's move ahead and create the Lambda function
   

4. Set up Lambda Function for Translation

   Perform the following steps to set up your AWS Lambda function:

   1. Login to your AWS Management Console, select AWS Lambda Service from the service list.
   2. Click on the Create Function button, and then the Author from Scratch option.
   3. Provide a name to your lambda function inside the Function name field, select Node.js 14.x as your Runtime language, and click on the Create function button. 
   4. Now in the Code source section, click on the Upload from dropdown and select .zip file.
   5. In the Upload a .zip file modal, click on the Upload button, contact our support team at support@contentstack.com to get the sample code. Then, click on Save.
   6. In the Runtime settings option, keep Handler as index.handler.
   7. Scroll up and select the Configuration tab.
   8. Click on the Environment Variable option on the left and add the following variables inside it by clicking on Edit and then Add environment variable.
   9. Next, set up the Environment variables as follows:
      
      CT_User: {Enter your Contentstack user ID}
      CT_Pass: {Enter your Contentstack password}
      memUser: {Enter your Memsource user name}
      memPass: {Enter your Memsource password}
      WorkFlowStage: {Enter the UID of the Review stage that we generated in step 2}
      Content_Type_Uid: {Enter the UID of your content type}
      source_Locale_Lang: {Enter the source local language, for example “en-us”}
      targetLocale: {Enter the target locale you created in step 1, in our example it is "ja"}
      targetTranslateLang: {Enter the target language of Memsource, in our example, it is "ja"}
      
   10. Once you have done these settings, click on Save.

   We have now set up our Lambda Function, we will now proceed with creating the API gateway to get the URL where our webhook will issue notifications.

   1. Log in to AWS Management Console and select API Gateways from the services list.
   2. Click on the Getting started or Create API button (depending on whether you have already an API configured or not).
   3. On the Choose an API type page, go to the REST API option (the public one) and click on Build.
   4. On the next page, ensure that Create new API section has New API checked. Under the Settings section, enter the API name and click on Create API. 
   5. On the next page, from the Actions dropdown in Resources, select Create Method.
   6. From the resultant dropdown, Select POST and click on the checkmark.
   7. Select your Lambda function in the Lambda Function field and click on Save. 
   8. You'll get the Add Permission to Lambda Function pop-up, click on OK.

   Next, we need to deploy our API. Follow the steps given below:

   1. Again, from the Actions drop-down in Resources, select the Deploy API option.
   2. Select [New Stage] in the Deployment stage and enter prod (or anything you want to identify this stage as) in the Stage name.
   3. Click on Deploy.

   On the next screen, you'll get your deployed API under Invoke URL. We'll use this URL in the next step when we create a webhook to initiate notifications to our Lambda function.

5. Trigger a Webhook to Initiate Translation

   To create and set up a webhook in Contentstack, log in to your Contentstack account and perform the following steps:

   1. Click the “Settings” icon (press “S”) on the left navigation panel and click on Webhooks (press “alt + W” for Windows OS, and “option + W” for Mac OS).
   2. Click on + New Webhook.
   3. On the Create Webhook page, fill up the Name field (for example, “Translation”). In the URL to notify field, enter the URL that you generated when you deployed your APIs, in the previous step.
   4. Scroll down to the Conditional View section for creating a trigger for the webhook as shown below:
      
      
      
      
   5. Once done, click Save to save your settings.

   With this, we have set up the webhooks for triggering notifications.

6. Try Out the Set-Up

   We are now ready to test the setup. 

   1. Go to your English (en-us) entry and change the workflow stage by selecting Send to Translation from the WORKFLOW DETAILS section on the right.
   2. Now select Japanese from the locale drop-down and you should see your entry translated in the target language, Japanese, and the workflow stage changed to Review. 

Tip: If you still cannot see your entry translated in Japanese, just hard refresh the page (Ctrl+Shift+R).