Winning AI search: The new rules for 2026 | Save your spot!
Contentstack
Changelog

Setting up a Translation System Using Contentstack Webhooks, AWS Lambda, and Smartling Machine Translation

Smartling is one of the most widely used cloud-based language translation platforms. It helps you to localize content across different digital properties. Through the APIs provided by Contentstack and Smartling, it is possible to integrate these two powerful applications.

In this guide, we will go through the steps required to set up a language translation system for your Contentstack-powered website by using Contentstack Webhooks, AWS Lambda, and Smartling that uses Machine Translation.

Additional resource: This guide discusses the steps required to translate content using the Machine Translation feature in Smartling. We have another guide that details out the steps required to set up a content translation system using the human translator feature in Smartling.

Process overview: We will first set up the essentials, such as creating a stack and one additional language, in Contentstack. We will create a workflow and add 4 stages in it namely Draft, Send for Translation, Review, and Completed. We will then create lambda functions that will help us create the bridge between Contenstack and Smartling for translation.

We will also set up a webhook such that when the workflow stage in an entry changes from Draft to Send for Translation, the webhook will issue a trigger to our first lambda function to initiate the translation process with Smartling. Once the content is translated by Smartling, it will invoke the second lambda function and update the content of the entry in the required language along with changing its workflow stage to “Review.”

Prerequisites


Steps for Execution

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

  1. Set up the essentials in Contentstack
  2. Set up the workflow for translation in Contentstack
  3. Configure your project in Smartling
  4. Set up the AWS lambda functions
  5. Trigger a webhook to initiate translation
  6. Try out the steps

Let's get started!

  1. Set up the Essentials in Contentstack

    To set up the essentials, log in to your Contentstack account and follow the steps given below:

    1. Create a stack, add a content type (for our exercise, we have created a Single Content Type named Smartling).

      Note: In our example, we have used “title,” “url,” “single_line,” and “rich_text_editor,” fields. We will translate the content of these fields. Content of special fields such as File, Boolean, Reference, Select will not be translated.

    2. Next, add two languages (locales), in our example, we have added the following two languages:

      1. English [en-us] which is the source language.
      2. French- France [fr-fr] is another language which will be our target language.

        Note: Ensure that the languages you add are supported by Smartling.

    3. Once you have added the languages, go to your content type (Smartling in our example) and create an entry in the en-us locale. 
    4. Lastly, create a management token for your stack which we will use later while setting up the lambda function. 

    With these steps, we have set up the essentials in Contentstack. Let's now move ahead with creating a workflow.

  2. Set up the Workflow for Translation in Contentstack

    To set up workflows for the translation process, perform the following steps:

    1. Hover over the “Settings” icon on the left navigation panel, and click on Workflows.



    2. On the Workflow Settings page, click on + New Workflow.



    3. Provide a suitable name to your workflow and an optional description.
    4. Under the Scope option, select if this workflow should be applied to All Content Types or Specific Content Type(s). For our example, we will select the Specific Content Types(s) option and then select our content type, Smartling from the dropdown menu, as shown below:
    5. Inside the WORKFLOW STAGES option, add four stages (for example, Draft, Send for Translation, Review, and Completed) as shown below:



      Additional resource: Learn more about workflow and its stages, refer to the set up workflows guide.

    6. Lastly, click on the Enable Workflow checkbox and then on the Save button.

    With these steps, our workflow is ready. Now when the editor changes the workflow stage from “Draft” to “Send for Translation,” the webhook will be triggered (we will set it up later in the guide) and call the first lambda function.

    Now go back to the Workflow Settings page and note down the WORKFLOW ID that we just created as shown below:


    We will need the UID of the Review stage which we will add as an environment variable while setting up our lambda function. To get the UID of the “Review” stage, open Postman or any other API collaboration & development platform and make a GET request on 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:
    • Refer to our workflow API documentation to learn more about the required headers to make an API request.
    • SSO-enabled organizations can use the management token to make API requests.

    You will get the following response:


    The highlighted UID in the above screenshot will be used in the lambda function's environment variable, so make note of it.

    Let's now move ahead and configure the project in Smartling.

  3. Configure Your Project in Smartling

    For this exercise, you need a full stack account with Smartling. You can sign up with one of their plans and get started with setting up your account. You may read through their getting started article.

    Create an MT Profile 

    The first part of setting up your project in Smartling is to create an MT Profile. To do this, and once you have the account set up, let's follow the steps given below:

    1. Log in to your Smatling account, click on the ACCOUNTS SETTINGS option, and select Integrations as shown below:


    2. On the Integrations screen, click on the Create MT Profile button as shown below. This profile is required by Smartling to know which machine translation provider service we will be using for content translation. Read more about Smartling MT Profile.


    3. In the Create MT profile modal, enter a suitable Profile Name. Then, select your machine translator provider from the MT Provider dropdown.

      Note: For our exercise, we have used Amazon Translate as the MT provider. You can choose the one that you have access to, or have an account with, for example, Google Translate, Microsoft Translator, and so on. If you select Amazon Translate, then provide the Access Key ID, Secret Key ID, and other values (AWS credentials). Similarly for other MT providers, provide the necessary details as required and proceed further.

    4. Ensure that the Enable MT Profile for Linguists in the CAT Tool option is switched On and then click on Save as shown below:


      Note: If you have multiple MT profiles, only the latest profile that you turned on will be enabled and other profiles (even if you turned them on before) will be disabled automatically.

    Your MT Profile is now created. You can test if the credentials are working by clicking on the Test Credentials button. If the credentials are working, you can move ahead with the next step which is creating a new project in Smartling.

    Create a New Project

    To create a new project in Smartling, log in to your Smartling account and follow the steps given below:

    1. Click on the SMARTLING icon at the top left corner. 
    2. Then, create a new project by clicking on Create New Project as shown below:



    3. On the Create Project screen, the Apple iOS is selected by default, leave it as is and click on Next.
    4. On the Project Details screen, provide a suitable name to your project. If you have already created a linguistic package earlier, then select it from the Linguistic package dropdown.

      If you haven't created any linguistic package yet, click on the Create New Package link. When you click on it, the Source Language dropdown appears. Select your source language, for example, English (United States), and then add your target language in the Target Languages field as shown below. For our example, we have added French (France) as our target language. Then, click on Create Project:


      Note: You can add more languages as your target language but French-France is selected as it is the requirement of this exercise.

    Your project is now created. Let's move ahead and create a workflow in Smartling.

    Add a Workflow for Your Smartling Project

    To do this, follow the steps given below:

    1. Click on the project that you just created, then on the Settings gear icon on the extreme right corner of the screen, and select Project Settings as shown below:



    2. On the Settings page, select Workflows from the left navigation panel.
    3. On the Workflow Configuration page, you will see a default workflow. Click on the dropdown icon inside the Translation block and select Manage Step as shown below:



    4. On the Manage Step: Translation screen, let the Step Name be Translation, select your MT profile you created earlier from the Translation Provider dropdown, leave the remaining options as it is, and click on Save as shown below:


    The Smartling Workflow is now ready. 

    Note: If you want to add more target languages to your project, click on the Project Settings option, and select Languages (similar to how you selected Workflows above). Then, click on the Add Language button. Then, in the Add Languages modal, add languages in the Select Language dropdown. Select Project Default from the Default Translation Workflow dropdown, Authorize all active strings from the Translation Authorization dropdown, and click on Add.

    Let's move ahead and create user and secret keys.

    Generate User Identifier and Secret Keys

    To do this, carry out the following steps:

    1. Click on the ACCOUNT SETTINGS dropdown at the top of the screen and select API.
    2. On the API screen, click on Create Token button inside the Project Tokens section as shown below:



    3. On the Create Project Access Token popup, select your project (if not already selected, from the dropdown) provide a name inside the Token Name field, and click on Create as shown below:



    4. Make note of the User identifier, Project ID, and User Secret keys as we will need these while setting up our lambda function.

    With these steps we have now configured our Smartling account. Let's move ahead and create the lambda functions.

  4. Set up the AWS Lambda Functions

    For this exercise, we will be creating two lambda functions. The first lambda function (once invoked) will take the content of the entry, write it into a file, and place it in the Smartling app for translation.

    The second lambda function gets invoked once the file (placed by the first lambda function) has been translated and then it updates the entry with the translated content along with changing the workflow stage of that entry to "Review."

    Set up the First Lambda Function

    Let's now create the first lambda function by using the steps given below:

    1. Log in to your AWS Management Console, select Lambda 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 12.x as your Runtime language, and click on the Create function button.
    4. You will get a success message on creation of the lambda function. If Extensions are part of your plan, contact our Support team to get the code for the extension. 
    5. Once you receive the code, use the file named before-translation, and upload it as a ZIP file by scrolling down to the Actionsdropdown (in the Function code section) and selecting Upload a .zip file as shown below: 



    6. Keep Handler as index.handler and click on Save. 
    7. Goto Environment Variable section, under Configuration tab and add the following variables to it, by clicking on Edit and then Add environment variable.



      apiKey: <<Your stack API key>
      baseUrl: https://api.contentstack.io (for Europe region, enter the value as https://eu-api.contentstack.com/. Similarly, for Azure NA region, enter the value as https://azure-na-api.contentstack.com, and for Azure EU region, enter the value as https://azure-eu-api.contentstack.com.)
      contentTypeUid: <<Your content type UID, for our example it is Smartling)
      managementToken: <<Your stack management token>>
      projectId: <<Your Smartling project ID we created above>>
      sourceLocale: <<Source language>>
      targetLocale: <<Target language>>
      userIdentifier: <<User user identifier key that we generated above in smartling>>
      userSecret: <<User secret key that we generated above in Smartling>>
      callbackUrl: <<API Endpoint of the second lambda function.>>
    8. Before saving the lambda function it is suggested to increase your function's timeout value. To do this, go to the Basic setting block, click on the Edit button, and increase the default time from 3 seconds to 29 seconds as shown below:



    9. Once you have made changes in the settings, click on the Save button. 
    10. Your lambda function is now ready. Scroll up to the Designer section and click on + Add trigger. 
    11. On the Add trigger screen, from the Select a trigger dropdown, select API Gateway. 
    12. From the API dropdown, select Create an API. Then, select REST API inside the API type block, select Open from the Security dropdown, and click on Add.



    13. An API for your lambda function is now created. Under the Designer block, click on API Gateway, you will see the Details link. Click on it and you will find your API endpoint. Make a note of it as we will need it while setting up our webhook in Contentstack.



    Let's move ahead and create our second lambda function.

    Set up the Second Lambda Function

    Let's set up the second lambda function which will be invoked once the translation gets completed. Follow the same steps, as mentioned above. But this time, use the file named after-translation and upload it as a zip file in your lambda function. Also, use the following environment variables while setting up the function:


    In the above screenshot, workflowStageUid is the UID of the Review stage that we retrieved using Postman. So enter the UID of the Review stage as the value for this environment variable.

    Follow similar steps to create an API trigger for this lambda function as well and use its API endpoint as the value of the callbackUrl environment variable in your first 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. Hover over the “Settings” icon on the left navigation panel, and click on Webhooks.
    2. On the Webhooks page, click on + New Webhook.
    3. On the Create Webhook page, fill up the Name field (for example, Smartling Translation). In the URL to notify field, enter the URL (the API endpoint of the first lambda function) that you generated in the previous step.
    4. Scroll down to the When section for creating a trigger for the webhook as shown below:



    5. Ensure to check the Enable Webhook option and click on the Save button to save your settings.

    With these steps, we have completed the entire set up and now we are ready to try it out.

  6. Try Out the Steps

    To do this, follow these steps: 

    1. Go to your entry in your content type (in our example, it is Smartling content type) and change the workflow stage by selecting Send for Translation from the WORKFLOW DETAILS section on the right side.

    2. Now select French - France from the locale drop-down and you should see your entry translated in the target language, French and the workflow stage changed to Review. 

    Additional resource: We have created similar guides that use AWS Translate and Memsource for content translation for Contentstack-powered websites. If you use any other platform besides the ones mentioned, you can still create the integration by following the steps mentioned in our Manage Content Translation in Contentstack guide.

More articles in "Translation Services"