# General Translation Platform: Automations
URL: https://generaltranslation.com/en-GB/docs/platform/locadex/reference/automations.mdx
Docs index: https://generaltranslation.com/llms.txt
Description: Manage Locadex automation templates, configuration, manual runs, targets, and activity. Reference for Locadex Automations.

Use **Project > Automations** for a single project or **Organization > Locadex > Automations** to work across projects.

Locadex workflows require a Starter, Team, or Enterprise plan. Creating, changing, or running an automation requires `project:locadex:write` for its project, including when you work from the Organization automation pages.

| Area                           | Description                                                      |
| ------------------------------ | ---------------------------------------------------------------- |
| [Automation lists](#lists)     | Search configured automations and start from templates.          |
| [Templates](#templates)        | Create code, translation, or locale synchronisation automations. |
| [Automation details](#details) | Review targets, status, configuration, and recent runs.          |
| [Manual runs](#manual-runs)    | Start an automation with its saved configuration.                |
| [Setup](#setup)                | Prepare a repository before its first automation run.            |

## Automation lists [#lists]

The project page contains:

* **Configured** — searchable automations for the current project
* **Start with a template** — templates for creating an automation
* **Recent activity** — the five latest runs across the project

The Organization page lists automations across projects. Search by automation or project, and choose 25, 50, or 100 items per page.

**Organization > Locadex > Integrations** lists the GitHub repositories available to Locadex and the project associated with each link.

## Templates [#templates]

* **Generate code** — detect untranslated user interface content and open a review pull request
* **Generate translations and push** — generate locale files from source changes and push an update
* **Keep locales in sync** — update project configuration after the locale list changes

The setup wizard selects one linked repository per project, a target directory, framework, target branch, trigger, branch prefix, and pull request behaviour. From the Organization page, you can create automations for up to 50 projects at once.

## Automation details [#details]

An automation detail page shows:

* Status and whether the automation is active
* Repository and target directory
* Framework, package manager, and linter
* Target branch and trigger
* Pull request, commit, and command settings
* **Recent runs**, including step status and customer-safe errors

Automations shared across multiple projects are visible but cannot currently be edited or run from the detail page.

**Preserve local edits** is enabled by default for new automations. When it is enabled, translation runs require either top-level `publish: true` or `files.gt.output` in `gt.config.json`. Keep it enabled to retain manual edits to previously generated translation files.

## Manual runs [#manual-runs]

Click **Run now** on an automation detail page to confirm its repository, target directory, and branch. A **Keep locales in sync** run also asks for the source locale and target languages.

## Setup [#setup]

An automation cannot produce correct results until its target directory is set up. Before setup starts, the detail page shows **Run setup**. While Locadex prepares the repository, the page shows **Setup is in progress**.

Choose the source locale and target languages, then start setup. Locadex prepares the repository and opens a pull request. Merge that pull request before running the automation. If setup fails, **Run setup** becomes available again so you can retry.

For server-rendered React frameworks, setup configures `gt.config.json`, translation loading, runtime initialisation, and [`GTProvider`](/docs/react/reference/components/gt-provider) placement. For client-rendered React applications, including Bazel and other SPA build systems, setup calls [`initializeGTSPA()`](/docs/react/reference/config#initialize-spa) before the application entry and configures browser translation loading. It then runs the repository's existing build or type-check command.

Setup does not wrap application strings with [`<T>`](/docs/react/reference/components/t) or other translation APIs; the **Generate code** automation handles source content after the setup pull request is merged.

## Sitemap

See the full [sitemap](https://generaltranslation.com/sitemap.md) for all pages.