globalize.now

Add (or update) glossary entries for a project in one call. Pass an array of term rows, each with its own source and target term and their project_language ids — so a single source term can have a different translation per target language. Resolve the language ids first with get_project. Entries are upserted on (project, sourceTerm, source, target); re-adding an existing key updates its target term and its do-not-translate flag. Set doNotTranslate on a row for a term that must be kept verbatim (a brand or product name); its stored target term is then forced to equal the source term. Both terms are trimmed of leading and trailing whitespace before they are checked and stored; a source term empty once trimmed is refused. Marks any matching translation-memory entries stale so future translations pick up the change. A project's glossary may be shared by other projects and Workflows in the organisation: a change to it applies to every one of them, and only the terms of the languages of the addressed project are listed or changed. The result's glossary.sharedWith names the others — tell the user which ones a change affects. While glossary.repositoryManaged is set, the glossary is synced from that project's asset repository and every write is refused. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Add a catalog language as a new target language on an existing project. Resolve the catalog language id first with list_languages. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Connect a Git repository to a project, optionally with locale path patterns. For GitHub, pass the githubInstallationId from list_github_installations. Registers webhooks and runs best-effort namespace discovery.

Create a localisation project from catalog languages. Resolve language ids first with list_languages. The source language is what your content is authored in; target languages are what it will be translated into. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Delete a single glossary entry by its id (from list_glossary) from a project in your organisation. Marks matching translation-memory entries stale so the affected content is re-translated without the removed term. A project's glossary may be shared by other projects and Workflows in the organisation: a change to it applies to every one of them, and only the terms of the languages of the addressed project are listed or changed. The result's glossary.sharedWith names the others — tell the user which ones a change affects. While glossary.repositoryManaged is set, the glossary is synced from that project's asset repository and every write is refused. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Delete the style guide for one target language of a project, keyed by its project_language id (from get_project or list_style_guides). When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Delete up to 200 entries, by id (from search_translation_memory), from the translation memory attached to a project, in one atomic call. Use it to remove faulty translations so future jobs stop reusing them. Ids that match no entry in that memory are reported as not found and nothing is deleted for them. A project's translation memory may be shared by other projects in the organisation: it holds their entries too (including languages this project does not translate into), and deleting an entry removes it for every project attached to the memory. The result lists those projects — tell the user which ones were affected. If the repository has reviewed translations in its target files, the next import brings a deleted entry back, so the faulty translation must also be fixed in those files. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Scan a GitHub repository to detect its framework, locale path patterns, source/target languages, and file format. Use the result to inform create_project and set_repository_patterns. Use the numeric installationId from list_github_installations.

Get a single project by its id or slug, including its languages and connected repository. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Get the style guide for one target language of a project — its full free-text translation instructions — keyed by the project_language id (from get_project or list_style_guides). When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Poll a translation job started by translate_files and, once it is "completed", pull back the translated files. While the job is still running, returns its status and progress with no file content — call again until status is "completed". A "completed" response carries each translated file (one per namespace × target language) plus a manifest; a "failed" response carries the failure reason. Optionally filter by target language to bound the payload of a large job.

Step-by-step instructions for adding multi-language support (i18n, translations, localization) to this Lovable app with Lingui and connecting it to Globalize. Call this FIRST, before editing any code, whenever the user asks to translate the app, add languages, internationalize, localize, or set up Globalize — then follow the returned instructions phase by phase.

One Workflow with its current version and definition. currentVersion.number is the baseVersion set_workflow_languages takes. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Poll a Workflow run: its status and failure reason, translated and total strings per language, each Output’s delivery outcome, the pull request a GitHub Output opened, and the run’s page in the Globalize app. A "completed" run has finished translating; it does not mean the translations were delivered. Its Outputs deliver after it completes: check each Output’s outcome (null until it has run, then delivered, failed or skipped) before telling the user the translations are in place. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

List the GitHub App installations available to your organisation. Use the returned numeric installationId with list_repository_branches, detect_repository, and connect_repository.

List the glossary entries for a project — each a source→target term pair with its languages and id. Optionally filter by source and/or target project_language id. Results are paginated; pass the returned cursor to fetch the next page. A project's glossary may be shared by other projects and Workflows in the organisation: a change to it applies to every one of them, and only the terms of the languages of the addressed project are listed or changed. The result's glossary.sharedWith names the others — tell the user which ones a change affects. While glossary.repositoryManaged is set, the glossary is synced from that project's asset repository and every write is refused. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

List the global Globalize language catalog. Optionally filter with a search term (matches language name or locale). Returns each language with the id and locale needed to create a project or add a project language. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

List all projects in your organisation — each project's id, slug and name with the id, name and locale of its source and target languages. get_project returns the full project. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

List the branches of a GitHub repository accessible to an installation. Use the numeric installationId from list_github_installations. Lists at most the first 1,000 branches in alphabetical order, plus the default branch (flagged) when it sorts later.

List the per-language style guides for a project — which target languages have one, with the guide id and the length of its instructions in characters. The instructions themselves are not included; get_style_guide returns one language's full text. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

The organisation's translation memories, newest first, each with how many entries it holds and how many projects and Workflows use it. An id here is the translationMemoryId preview_workflow_setup and set_up_workflow take. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

A Workflow’s runs, newest first, each as get_workflow_run reports it. Cursor-paginated. A "completed" run has finished translating; it does not mean the translations were delivered. Its Outputs deliver after it completes: check each Output’s outcome (null until it has run, then delivered, failed or skipped) before telling the user the translations are in place. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

The organisation's Workflows, archived ones included: what each reads, its target languages, its current version and its most recent run. get_workflow returns one with its definition. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Preview setting up a Workflow that translates a GitHub repository, from the App installation id (list_github_installations) and "owner/repo" alone. Detects the locale files on the first branch and proposes a definition: Translate, then QA, delivered by pull request; the detected source and target languages; named "owner/repo". Writes nothing and starts no run. Answers ready: true with the definition, the file groups left out as unlikely (excludedGroups) and a previewHash for set_up_workflow; or ready: false with needs (each names what was found and the argument to pass — a language is never guessed), or with alreadySetUp naming the Workflow that holds the repository, whatever any Project on it does. Only when no Workflow holds it is it refused with REPOSITORY_HELD_BY_PROJECT, when a Project has work on it: continue on that Project. Pass the optional arguments to apply what the user asks for. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Remove a target language from a project. Pass the project_language id (from the targetLanguages list returned by get_project), not a catalog language id. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Search the translation memory attached to a project — the stored source→translation pairs that future jobs reuse as-is when the same source text comes up again. Filter by a case-insensitive substring of the source or translated text, and/or by source and target locale. Returns each entry with its id, texts, languages, notes and context. Results are paginated; pass the returned cursor to fetch the next page. Use it to find faulty entries and pass their ids to delete_translation_memory_entries. A project's translation memory may be shared by other projects in the organisation: it holds their entries too (including languages this project does not translate into), and deleting an entry removes it for every project attached to the memory. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Set a project's project-wide context — the free-text prompt guidance shared across every target language (what the product does, its audience, tone). At most 1000 characters. Read the current value with get_project. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Add locale path patterns to a connected repository (existing identical patterns are skipped). Each pattern must contain exactly one {locale} and at most one {namespace}.

Create or replace the style guide (free-text translation instructions) for one target language of a project, keyed by its project_language id (from get_project). You draft the instructions yourself, at most 60000 characters. A brand-new guide always marks that language's translation memory stale so future translations follow it; for an update, set recheckExistingTranslations to also re-check already-translated content (it defaults to off). When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Set up the Workflow preview_workflow_setup proposed: pass the same arguments plus its previewHash. Publishes the definition as version 1 and creates a translation memory unless one was named. Refused when anything changed since the preview (WORKFLOW_PREVIEW_STALE, with the fresh preview), and when a Workflow already holds the repository (WORKFLOW_REPOSITORY_CLAIMED), so a retry never creates a second one. Starts no run: start_workflow_run does, once the user agrees to spend credits. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Replace the target languages a Workflow declares, publishing its next version with nothing else changed. Pass baseVersion, the version number the change starts from (get_workflow): refused with WORKFLOW_BASE_VERSION_STALE when another version was published since, so a concurrent edit is never overwritten. The same languages publish nothing (published: false). When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Begin connecting GitHub. Returns an install URL — surface it to the user to open in a browser and install the Globalize GitHub App. After they confirm, call list_github_installations to get the installation id.

Start a run of a Workflow’s current version, which spends credits: start one only when the user agrees. A GitHub Workflow translates its primary branch unless given a watched branch, and delivers by pull request unless delivery: "push". A Workflow reading a Contentful space runs over its whole selection and takes neither argument (refused with VALIDATION_ERROR). Refused with INSUFFICIENT_CREDITS (402) when the organisation is out of credits, and with WORKFLOW_AWAITING_CONVERSION_MERGE (409) while the pull request of the Conversion that created the Workflow is open (only it starts runs until it is merged; the error names it). Returns the run at once; poll get_workflow_run. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

Submit one or more source files to be translated as a single job. Each file is parsed by its content (JSON — flat, nested, ARB and Chrome/WebExtension messages.json — plus PO, XLIFF 1.2 and 2.0, YAML, @wxt-dev/i18n TOML/JSON5/JSONC catalogs, Android XML, iOS xcstrings, Markdown and HTML), so pass the file as-is. Target languages default to the project's configured target languages; pass a subset to translate only some. Returns { jobId, status }. Translation runs asynchronously. This call returns immediately with a jobId; it does NOT wait for translation to finish. Call get_translation with the jobId and keep calling it until status is "completed" (or a terminal failure), then read the files.

Start translating a connected repository: the locale files on the branch are translated into the project's target languages and delivered back to the repository, by default as a pull request. Runs in the background; this call returns once the translation is queued. Refused when the organisation is out of credits, when the repository has no locale path patterns (see set_repository_patterns), or when a Workflow handles the branch. The id is connect_repository's id, or the connected repository get_project returns.