Translation Manager for Confluence
Export Confluence Cloud pages as HTML, translate them in your preferred translation tool, then import them to create or update translated pages.
This guide covers version 1.0.0 of the Windows app.
Connect to Confluence and Settings
1. Install, connect to Confluence, and Settings
Install Translation Manager for Confluence from Microsoft Store and open it from the Start menu. You need an internet connection and a Confluence Cloud account with permission to read your source pages and create or update pages and attachments.
1. Open Settings.
2. Enter your Confluence site URL, such as https://your-company.atlassian.net.
3. Enter your Atlassian email and API token.
4. Click Test connection, then Save settings.
An API token lets the app connect using your Atlassian account. To create one, open Atlassian API tokens, select Create API token, give it a name, and choose an expiry date. Copy the token into the app.
For version 1.0.0, use Create API token, rather than Create API token with scopes.
Enable Remember API token to save it in Windows Credential Manager. Otherwise, enter it again when you reopen the app.
In Settings, you can also choose System, Light, or Dark appearance.
Edit the language list
In Settings, select Open languages file. The shared file is %APPDATA%\AiqaraTranslationManager\languages.csv. It supplies the source and target choices on Export and the target-language choices on Import. The import source language remains part of the exported record rather than a separate editable dropdown.
Keep the header code,name. Add one language per row, for example:
code,name
en-GB,English United Kingdom
es-US,Spanish United States
Save as a UTF-8 CSV and restart the app. Regional variants use separate codes. Avoid duplicate codes and blank names. An invalid file causes the app to use its default list and show a warning. Existing imported records can retain language codes no longer present in the dropdown.
Save a diagnostic log
Go to Settings and select Save diagnostic log. Choose a location, review the text file for confidential information, and attach it to your support request to support@aiqara.com. Include your app version, what you were doing, and approximately when the error occurred. Never send an API token.
Logs are recorded while the app runs. Saving a log exports retained records; it does not start a new recording. Earlier sessions can therefore appear in the file. The original diagnostics are in %APPDATA%\AiqaraTranslationManager, with a current log and up to two rotating backups. Saving does not automatically send anything to Aiqara.
Export a Page From Confluence
2. Export a page
Use Export page when you want to send a Confluence page for translation.
-
Copy the URL of the Confluence page.
-
Paste it into Choose a Confluence page.
-
Click Load page.
-
Check the source page details.
-
Select the Source language.
-
Select the Target language.
-
Click Export HTML for translation.
-
Choose where to save the HTML file.
The exported HTML includes the page title, page content, and information identifying the original Confluence page.
The HTML file can then be translated using your preferred CAT tool or translation workflow.
Important: Keep the Aiqara HTML structure and metadata in the translated file. This allows the Translation Manager to identify the original source page when the file is returned.
Import a Translation to Confluence
3. Import a translation
Select the translated HTML file.
The application automatically reads:
-
the source page;
-
the target language;
-
the translated page title;
-
the source information stored in the exported HTML.
You can edit the Translated title before publishing if required.
Under Import mode, choose one of the two options:
Create new page
Choose Create new page when this translation has not yet been published.
Click Review new page.
The new translated page will be created in the same Confluence space as the source page, directly below the original source page. You can move the page within Confluence afterwards if required.
Review the information shown and click Create page.
Update existing page
Choose Update existing page when a translated page already exists.
The application looks for translations previously linked to the same source page and language. If one is found, it appears in Translation to update.
-
Select the translated page.
-
If necessary, paste the URL of an existing translated Confluence page directly into the field.
-
Click Review update.
-
Check the destination carefully.
-
Click Update page.
Updating replaces the content of the selected translated page. It does not create another page. The application also checks the page version before updating, helping prevent an unnoticed overwrite if the page changed after review.
Review before publishing
Before anything is written to Confluence, the app displays a review window.
For a new page, it shows:
-
Title
-
Language
-
Source page under which the translation will be created
For an update, it shows:
-
Title
-
Language
-
Existing page that will be updated
You can also click Open destination ↗ before confirming.
History
History
Open History to view previous exports and published translations.
History shows:
-
Source page
-
Language
-
Status
-
Translated page
-
Date
-
available actions
Use ↗ to open the relevant Confluence page.
Use the trash icon (🗑) to remove an item from the Translation Manager’s history.
For a published translation, removing the history item also removes the saved translation relationship used by the app.
It does not delete the actual Confluence page.
You can also use Search history to find previous exports or translations.
Troubleshooting & FAQ
Connection or publishing errors from Confluence A 404 error does not always mean the page was deleted. Check whether your API token has expired, confirm the Confluence site URL, and make sure your account has the required permissions. For authentication or permission errors, check the email and API token, then test the connection again. For HTML-related errors, compare the translated file with the original export and make sure the technical HTML structure and values have not been altered.
No linked page found If you have only exported a page from Confluence, there may be no translated page yet: use Create new page first. If the target already exists, check the source page, language code, connected site and saved history, refresh available links and use the target URL if necessary. Do not select an unrelated page merely to bypass the message.
Arabic and other right to left languages Confluence Cloud has limitations with right-to-left layouts. Arabic, Persian, Hebrew and other RTL content may not preserve all direction and layout settings after publishing. Always review the published page in Confluence.
A timeout or warning after publishing Check the destination in Confluence before trying Create again. A request may have reached the server even if the response was lost. A page can also publish successfully while saving its translation link fails. Repeating creation without checking can produce duplicates. Save the log and retain the page URL for support.
Files and uninstalling Settings, history, languages and logs are normally stored under %APPDATA%\AiqaraTranslationManager. Exported HTML and saved diagnostic copies remain in the folders you chose. Treat them as potentially confidential. Uninstalling the app does not necessarily remove these files or stored credentials. Published Confluence content remains on the site.
Support and product information Help website: https://www.aiqara.com/translation-manager-for-confluence/how-to Support: support@aiqara.com Privacy: https://www.aiqara.com/privacy
Built for flexible localization workflows
Any language or locale
Add the language or locale you need manually, so you are not limited to a fixed list.
Easy import, export & updates
Export Confluence content for translation, import it back, and update existing translated pages without rebuilding them.
Low-cost workflow
Keep the process lightweight and avoid unnecessary platform or integration costs.
Get Translation Manager for Confluence
Install the Windows app and start moving translated content between Confluence and your localization workflow.