Define translation triggers and react to them

Jiri Lojda, Ondrej Chrastina

2 minutes

Download PDF

0% complete

Decide what action in Kontent.ai triggers your translation process and how you want to respond to it.

Choose what triggers the translation

A. Move an item to a specific workflow step

The easiest approach for triggering the translation process is changing a content item’s workflow step.

➕ Advantages	➖ Disadvantages
Prevents users from editing the item while it’s being translated. Provides a clear overview of all items being translated, for example, by filtering by workflow step.	The item’s content might be in an invalid state due to incomplete elements.

B. Trigger from a custom app or custom element

Use a custom-built app to trigger the translation process. Optionally, you can include the app as a custom element in Kontent.ai.

➕ Advantages	➖ Disadvantages
Offers the most customization options.	Content creators might forget to trigger the translation process. Doesn’t enforce the translation workflow. Requires you to insert the custom app somewhere outside the content item. The item’s content might be in an invalid state due to incomplete elements.

C. Publish an item

Trigger the translation process when users publish a content item.

➕ Advantages	➖ Disadvantages
Ensures the item’s content is in a valid state without any incomplete elements.	You need to publish content in the source language before you receive translations from your TMS. This means you cannot publish your content in all languages at once. If users create a new version of the published item, you cannot retrieve the published version via Management API.

Respond to the trigger

Once you decide what action triggers your translation process, you need to respond to the trigger. That means you need to know when the action happened.

Wait for webhook push notifications

Sign in with your Kontent.ai credentials or sign up for free to unlock the full lesson, track your progress, and access exclusive expert insights and tips!