Automations are available in the Autopilot plan

How to create Automations #️⃣

To create your first automation, navigate to Tools -> Automations in your project and click on the NEW AUTOMATIONS button.

Only project Managers and Owners can create and manage automations

Configuring Automation #️⃣

Each automation consists of three parts. The automated action, triggering event and optional event filters. These parts are configured in a three-step form. As you build the automation, the right side panel will help you understand what action and under which circumstances will run based on the configuration form.

Automated Action #️⃣

In the first step you may choose one of the available automation actions. We will cover each action in greater detail later in this article.

Unique Automation names are generated automatically based on the selected action. You may rename the Automation in the top right area of the configuration form.

Trigger event #️⃣

Select a trigger event based on the selected Action. This section is where you configure when the Action should run, for example, on key/translation upload or update.

Available Trigger Events depend on the Action you selected because, for some Actions, some Trigger Events wouldn’t make any sense.

Updated source key or translation

Runs when keys or translations are updated through upload (CLI, API or manual upload)

Imported new source key or translation

Runs when new keys or translations are created through upload (CLI, API or manual upload)

Manually created source key

uns when new keys are created directly in Localazy

Source key deprecated in import

Runs when keys are marked as deprecated during upload (CLI, API or manual upload)

Translated Source key

Runs when a new translation is added (included new unapproved version awaiting review)

Reviewed transation

Runs when a translation is reviewed (both approve and reject)

Filters #️⃣

By default, Automations are run on all events (all selected triggers). You can specify conditions that must be met to run the workflows in this section.

Filter by the Translation State

You can choose which translation states this Automation will apply to. E.g., only to translations that are waiting for review or those that are set as source changed.

Filter by Language

Choose the languages for which the Automation will run. For some automated actions you may only choose one language, for others multiple.

Filter by User triggering the event

Select which project or system users you want to include or exclude from this Automation. The user depends on the trigger event. For example, an Automation run on the Translation Reviewed trigger event would consider who reviewed the translation, not who created it.

For example, you can configure a workflow that will set all translations made by Localazy MT user as needing improvement - this way, all translations made by machine translation engines will be immediately sent for another round of translation by human translators.

The system users are special Localazy users who may be author of translations under certain circumstances.

• Localazy Importer - Whathever you import into Localazy, i.e., the translations imported when you started the project and not created in Localazy.
• Localazy InTM - Translation created by applying Localazy Translation Memory
• Machine Translation - Translation created by using machine translation
• Localazy translation service - Translation created by Localazy’s Continuous Localization Team.

Filter by User Role

This filter compares the user role, which is the same user as in User-based filtering, with the selected list. You can choose from a Translator, Trusted Translator, Reviewer, Manager, Owner.

Filter by Tags

Select which source key tags to include or exclude from the Automation

Filter by Priority

Select which source key priorities to include or exclude from the Automation. Commonly used with Use Machine Translation action to automatically translate source keys with (usually) low or lowest priority.

Filter Content

Apply the Automation only to cases with specific content. You can choose to include or exclude source key names, translations, comments and files that contain some words or follow a regular expression.

Filter Source Text with AI

Use Localazy AI to analyze the inputs and determine whether the Automation should run or not.

Tip: This filter is great for the “Set as Needs Improvement” Action. Localazy AI can act as a pre-reviewer and tell you which translations might contain problems based on your criteria.

You can use Sentiment analysis, set a preferred gender, formality of the tone, or include/exclude translations with offensive wording or cultural issues. You can also use the AI to detect if the translation provided is in another than expected language and set a range of readability scores to decide which translations pass this check.

Filter Translation with AI

Currenlty available only for the Merge project updates into another branch action, this filter processes source key translation for each included language.

Available automated actions #️⃣

Here’s an overview of all Actions currently available for your Automations.

Use machine translations #️⃣

Automatically translate source keys using a machine translation engine of your choice to selected languages. You can also specify if you want to send these translations to the Review process and apply to translations in the source changed state or those with existing translations waiting for review.

Apply translation memory #️⃣

Automatically translate source keys using Translation Memory for selected languages. You may include additional the sources of Transaltion memory when you connect your other projects using the Connected Projects feature.

Merge project updates into another branch #️⃣

When your project uses the Project Branching feature, you may automatically merge project updates for selected languages from one branch into another (both into ancestor and descendant branches).

You can also specify whether you want to create new files, new languages or new keys in the target branch, or only update existing ones. You may also control whether to deprecate missing source keys in the target branch or if you want to overwrite existing translations.

You may choose from project branches in which you have the Owner role. You cannot automatically merge updates into branches in which you have lower than Owner role.

Update “Needs improvement” state #️⃣

Automatically set or clear the ‘Need Improvement’ flag for translations that pass the filters.

Copy translation to another language #️⃣

Automatically copy translations from one language to another when keys are created or updated. Select the target language and decide whether to send the copied translation to the review process, even if the original one is automatically approved.

Tip: Use the language filter to specify the language from which you want to copy translations

Hide source keys #️⃣

Conditionally mark keys as hidden based on triggers and filters. Useful if you want to prevent translation of certain source keys, .e.g. brand names or abbrevations.

Show source keys #️⃣

Conditionally mark keys as not hidden based on triggers and filters. May be useful in combination with other automations, e.g. when you want certain keys to be translated only once other source keys have been translated.

Delete deprecated source keys #️⃣

Automatically remove keys that were marked as deprecated. Make sure to check the trigger as well.

Update “Source changed” state #️⃣

Automatically set or clear the ‘Source changed’ flag for translations that pass the filters.

Update source key tags #️⃣

Add or remove source key tags based on triggers and filters. Often defined together with the Content filter to add source key tags based on the file the source keys are included in.

Update source key priority #️⃣

Set priority source key tags based on triggers and filters. Often defined together with the Content filter to set a priority for source keys included in a specific file.

Automations overview #️⃣

Once you have at least one existing Automation, you will see the overview of Automations alongside with basic information for each one, including the last run timestamp.

Order #️⃣

The automation are triggered in order in which they are listed, starting from the one on top. You may change the order by clicking on the six bullets icon on the left side of each Automation tile and dragging it up or down.

When you have multiple automations that are triggered by the same event, the final state may differ based on the order in which the automations are run. For example, when you have two automations “Apply translation memory” and “Use machine translations” in this order and trigged by Imported new source key or translation event, then new source keys will be first attempted to transalte using the translation memory and only the remaining untranslated source keys will be processes and translated by machine engine. However, if the automations were defined in the opposite order, then all source keys will be translated by the machine engine and there won’t be any source key left untranslated for the translation memory automation.

Available actions #️⃣

In the Automations overview, there are a various action available for each automation

• Edit - opens the automation configuration form
• Disable or Enable - you may disable enabled (or enable) disabled automation. A disabled automation won’t run until re-enabled
• Delete - Delete the automation permanently
• Duplicate - Create an exact copy of the automation

Automations events log #️⃣

You may find basic information about runs of the automation after its first occurence.