Translate
Support in any language without leaving GLPI
Translate works right in the GLPI timeline: it translates the description, follow-ups, tasks, approvals and solutions of tickets, problems and changes, without copying text into external tools. Each item gets a translation switch. When it is on, the text is shown in the language the person uses GLPI in, in place of the original; when it is off, the original comes back.
FreeGLPI 11 and 12
Features
You choose the provider that fits best: DeepL, Google Cloud Translation or an AI model (OpenAI, Gemini or Claude). Just enter the API key in the module panel and test the connection right there, before rolling it out to the team.
To keep cost and performance under control, each translation stays cached for the number of days you set and is redone automatically when the original text changes. Items above the character limit are not sent to the provider. The module respects the visibility of each ticket, including private follow-ups and tasks, can be limited to specific entities and has a log with an adjustable level. Completely free.
How it works
Step 1
Choose a provider
In the Translate panel, select DeepL, Google Translate or AI, enter the API key and test the connection right there.
Step 2
Choose what to translate and the limits
Choose which items can be translated (description, follow-ups, tasks, approvals and solutions), the enabled entities, the cache retention and the character limit per item.
Step 3
Translate in the ticket
On a ticket, problem or change, the technician turns on the item's translation switch and reads the content in the language they use GLPI in, without leaving the page.
See it in action
A quick tour of what the plugin does in practice.
Video demo coming soon.
Image gallery
Screenshots for this section are coming soon.
Start using Translate
View available plans or read the full article about this module.