How to Translate Tickets in GLPI with DeepL, Google or AI

Meet Translate, NexTool's free module that translates tickets and follow-ups directly inside GLPI on demand, using DeepL, Google Translate, or AI (OpenAI, Gemini, or Claude).

Handling a user who opens a ticket in another language stalls the workflow: the technician copies the text, pastes it into an external translator, comes back, replies — and repeats with every follow-up. NexTool's Translate module eliminates this back-and-forth by translating tickets and follow-ups right inside the GLPI interface, on demand and in the language the technician chooses.

Inspired by the behavior of Teclib's translation plugin, Translate is a free alternative for support teams that serve customers or branches in more than one language. Instead of relying on external tools, translation happens in the context of the ticket, preserving the history and respecting the ticket's visibility permissions.

Three translation providers, you choose

Translate doesn't lock you into a single service. In the module panel, choose the provider that best balances cost, quality, and privacy for your operation:

  • DeepL — the benchmark for quality in European languages, with natural and fluent translations.
  • Google Translate (Google Cloud Translation) — broad language coverage and high availability.
  • AI (LLM) — models from OpenAI, Google Gemini, or Anthropic Claude, for translations with context and a tone closer to human.

Simply enter the API key for the chosen provider and use the built-in connection test to validate the configuration before making it available to the team.

Per-item translation, on demand

Nothing is translated automatically without need. Each technician activates translation on the item they need — the ticket description or a specific follow-up — and sets the target language. The language preference is saved per user, so technicians handling international clients keep their configured language without reconfiguring on every ticket.

Cache and limits to control costs

Since translation providers charge by volume, Translate was designed to be economical:

  • Translation cache with configurable retention (in days): the same content is not translated — nor charged — twice.
  • Size limit per item: items exceeding a character count can be skipped, avoiding costs for very long texts.
  • Translation log: track what was translated, by whom, and with which provider.

Free and ready for GLPI 11

Translate is distributed free of charge through the NexTool module catalog and runs on GLPI 11 on top of the NexTool base plugin. Installation follows the same process as any other module: activate it from the catalog, configure the provider and target language, and the translate option will appear on tickets.

If your team wastes time switching between GLPI and translation tools, Translate gives that time back to support — with no license cost and the flexibility to choose the provider that makes sense for your scenario.

Frequently Asked Questions

It is a free module for GLPI 11 that translates tickets and follow-ups directly in the GLPI interface, on demand, using DeepL, Google Translate, or AI (OpenAI, Gemini, or Claude). It avoids copying text to external translators during support.

Three: DeepL, Google Translate (Google Cloud Translation), and AI models from OpenAI, Google Gemini, or Anthropic Claude. You choose the provider in the module panel and enter the corresponding API key.

No. Translation is per item and on demand: the technician activates translation on the description or the follow-up they need, in the chosen target language. The language preference is saved per user.

Through a cache with configurable retention (the same content is not translated twice) and a size limit per item. All translations are recorded in a log.

Yes. Translate is distributed free of charge through the NexTool catalog. You only need an API key from the chosen translation provider (DeepL, Google, or AI).

Need help?