Translate the page,
then get it approved
Open a culture-varying page, pick the target language, start. The agent translates the node name, rich text and Block List content into a draft in the target culture only, then routes it to a reviewer by email. Approved content goes live. Nothing else does.
Free on the Umbraco Marketplace. Translation Pro adds batch translation, Azure Translator and a termbase.
From draft
to approved
Send for approval picks a reviewer from your backoffice users. They get a read-only preview and a direct link to the variant, approve or decline with a note from the workspace footer, and reminders chase pending reviews automatically. Every review is listed on the Translation Workflow dashboard.
Structure stays intact
Rich text keeps its tags, Block List and Block Grid keep their GUIDs and aliases. Only human-readable text is translated.
Style from what you published
Point at pages already translated and their approved translations become the agent's tone and terminology examples.
Dictionary items too
Translate dictionary items from the same view - free in every edition.
Translate
at scale
Pro ships inside the free package. A licence key, validated offline, unlocks three things.
Multi-page and entire-site batches
Translate many pages, optionally with all children, in one run - with one approval email for the whole batch.
Azure Translator engine
More than 100 languages through your own Azure Translator resource: deterministic, fast, and far cheaper for bulk work.
Enforced termbase
A glossary of approved translations and do-not-translate terms, applied on every translation - content and dictionary alike.
FOR DEVELOPERS
Up and running in four steps
The short version. The full guide with screenshots, configuration reference and troubleshooting is in the developer docs.
-
1 · Prepare the site
Umbraco AI with a chat profile, content types that vary by culture with the target languages added under Settings → Languages, and SMTP under Umbraco:CMS:Global:Smtp for the approval emails.
Backoffice -
2 · Install the package
dotnet add package Flowcourier.Umbraco.AI.Agents.Translation. The agent registers itself with the Copilot and creates its review table on the next startup.
Terminal -
3 · Grant the Translation section
Reviewers and editors who use the Translation Workflow dashboard need the Translation section under Users → Groups. Reviewers must be backoffice users with an email address.
Backoffice -
4 · Optional: tune the workflow
Flowcourier:TranslationReview sets PublishOnApprove, reminder timing and the maximum number of reminders. A Translation Pro key goes under Flowcourier:Licenses:TranslationPro.
appsettings.json
What do I need before installing?
Umbraco 17.5 or later with the Umbraco AI Copilot and a chat profile, content types that vary by culture with the target languages added, and SMTP for the approval emails.
Is the source language ever touched?
No. The agent saves a draft in the target culture only. The source variant is never modified.
What happens without a Pro licence?
Single-page translation, the review workflow and dictionary translation keep working exactly as in the free package. Only batch runs, the Azure engine and termbase edits need a key.
Where does my content go?
To the LLM behind your own Umbraco AI chat profile, or to your own Azure Translator resource. Never through Flowcourier.
See the Translation Agent in action
Book a demo and we walk through a translation, the approval email and the reviewer's side on a live site.