Integration · Sell and serve

DeepL and Meteor AI agents

Connect DeepL to a Met: translate messages with your glossaries and style rules, rewrite and correct texts with the official MCP.

Book a demo See every integration

How does DeepL connect to Meteor?

With the DeepL ready connector, your Met translates with your DeepL account. It translates a text into the language you ask for, detects the source language by itself if you do not give it, adjusts formal or informal tone and follows the glossaries and style rules your team saved in DeepL. It also rewrites a text in the same language or another one and corrects errors. It helps you serve customers who write in another language on WhatsApp with your business's terminology. Usage runs on your DeepL plan.

What it automates

What a Meteor Met does with DeepL

Serve customers in their language

When a customer writes in English or Portuguese, the Met translates the reply with DeepL into the customer's language, with the tone you defined.

Keep your business terminology

If your team has a glossary in DeepL, the Met uses it when translating so your product and service names always come out the same.

Rewrite a message before sending it

The Met rewrites or corrects a text, such as a reply template or an announcement, so it reads clearly and without errors.

11 tools

Everything your Met can ask DeepL for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`translate_text`	Translates a text into another language, with glossary, style rule and formal or informal tone if requested.
`rephrase_text`	Rewrites a text, in the same language or another one.
`correct_text`	Corrects the errors in a text.
`get_source_languages`	Lists the language codes DeepL accepts as a translation source.
`get_target_languages`	Lists the language codes DeepL can translate into.
`list_glossaries`	Lists the account's glossaries with their name, dictionaries and creation date.
`get_glossary_info`	Returns the details of a specific glossary.
`get_glossary_dictionary_entries`	Returns the terms of a glossary dictionary, for a language pair in one direction.
`list_style_rules`	Lists the account's style rules with their name, language and dates.
`get_style_rule`	Returns a full style rule, with its rules and custom instructions.
`get_custom_instruction`	Returns a custom instruction that belongs to a style rule.

The limits

What the DeepL integration does NOT do

We would rather say it here than have you find out during rollout.

It does not translate documents in this listing. The server has document tools, but how it receives the file was not verified, so they are not listed here.
It does not create or edit glossaries. The tools in this listing read glossaries and style rules; they are created and edited in DeepL.
It does not use a glossary without the source language. DeepL requires the source language when the translation uses a glossary.
It does not pay your DeepL plan. Usage runs on your account; Meteor does not resell the service.

Before you start

What you need to connect DeepL

1

A DeepL account

Your business's DeepL account. The glossaries and style rules you want to use are created in DeepL before connecting.
2

Connect it in Met

In Met, open Connections → DeepL → Connect. A DeepL window opens so you sign in and authorize Met.

Frequently asked questions

Questions about DeepL and Meteor

Yes. If the source language is not given, DeepL detects it by itself. Only with a glossary does it need to be stated.

Yes, in the languages where DeepL allows it: translation accepts a formality level. Where the language does not support it, DeepL uses its default form.

If you save them in a DeepL glossary, the Met uses it when translating and the names come out the same in every message.

You do, with your DeepL account and plan. Met does not charge for the translations your Met asks DeepL for.

Step by step