Resources · Make integration

DeepL Make integrationAutomate DeepL with Make.

Can Make send your text to DeepL and bring the translation back on its own? Yes. The DeepL Make integration gives you 2 action modules, no trigger. This guide shows how to plug in your API key, build a first scenario and pick the right module.

Try the DeepL integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the DeepL Make integration do for you?

The DeepL Make integration lets a Make scenario (the automation you build, a chain of steps) hand a piece of text to DeepL and receive it translated into the language you pick. You set it up once. After that, every new text that reaches the scenario gets translated without anyone copying and pasting.

Product pages in several languages. An online store writes its descriptions in English. A scenario picks up each new description, runs it through Translate a Text and passes the result to the next app, so the German and Spanish versions are ready to review.

Support tickets you can actually read. A customer writes in Italian, your agents read English. The ticket text goes through DeepL first, and the translation lands next to the original in your help desk.

Anything the listed module skips. Make an API Call reaches the rest of the DeepL API with the same connection, for the cases the translation module does not cover.

Keep in mind that DeepL has no trigger in Make: it never starts a scenario by itself. Another app or the schedule does that, and DeepL does the translating in the middle. If you are still weighing the platform, the Make review walks through it, and Make pricing explains how operations are counted. The same app also exists as a node in n8n: see the DeepL n8n integration.

Connect

How do you connect your DeepL account to Make?

  1. 01

    Copy your DeepL API key

    You need a DeepL API account with an API key. Open your account on DeepL, go to the API Keys and Limits tab and copy the key shown next to your active key. Keep that tab open, you paste it in a moment.

  2. 02

    Open the connection window

    In your scenario, add any DeepL module and click Create a connection. A connection is your DeepL account linked to Make once; every DeepL module in your scenarios reuses it afterwards.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name like "DeepL marketing" helps when you have several accounts. Paste the API key and confirm. From now on, every DeepL module can pick this connection.

First scenario

Your first scenario with DeepL and Make

GoalWhen a text reaches the scenario, Make sends it to DeepL, gets the translation back and passes it to the next step.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. Search for DeepL and pick Translate a Text.

  2. 02

    Link your account

    Click Create a connection and paste your API key, as described above. Once the connection exists, Make can fill the module with what it reads from DeepL.

  3. 03

    Tell DeepL what to translate

    Fill the module: the text to translate and the language you want. To start, type a short sentence by hand so you can check the result before wiring in real data.

  4. 04

    Add the next module

    Click the + on the right of Translate a Text and add Make an API Call if you need another part of the DeepL API. Map the translation from the previous module into it.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received (a bundle is one item passing between modules, here one text). Read the translation there.

  6. 06

    Schedule and switch on

    Since DeepL has no trigger, the clock on the first module decides when it runs: every 15 minutes by default. Adjust it, then switch the scenario on.

Modules

What the DeepL modules do

DeepL gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

DeepL1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module is the open door to the whole DeepL API. It sends a request you write yourself, signed with the connection you already created, so you never paste the key twice.

When to use it
the moment you need something from DeepL that Translate a Text does not offer, pick this one instead of looking for another app.
Watch out
you describe the request yourself, so keep the DeepL API reference open while you fill it in.
DeepL2

Translate a Text

Action

In Make“Translates a text into specified language.”

Give it a piece of text and a target language, and it returns the translated version as a new value you can map into any following module. Each run on one bundle costs one operation, the unit Make counts on your plan.

When to use it
a product description, a ticket or a form answer arrives in one language and the next app needs it in another.
Watch out
a scenario that feeds it many texts at once uses one operation per text.
Need help

Need help automating DeepL with Make?

A person reads every message.

FAQ

Questions people ask about DeepL and Make

01Is the DeepL Make integration free?
Yes, on the Make side. DeepL is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. DeepL itself is a separate account: you still need a DeepL API account and its API key to connect.
02What do you need to connect DeepL to Make?
Two things: a Make account and a DeepL API account with an API key. In DeepL, open your account, click the API Keys and Limits tab and copy the key next to your active key. In Make, add a DeepL module, click Create a connection, optionally type a connection name, then paste the key. That single connection is then reused by both DeepL modules in every scenario you build, so you only do this once per DeepL account.
03Can DeepL start a Make scenario in real time?
No, because DeepL has no trigger module in Make. It only acts once a scenario is already running. To get things moving, either put a trigger from another app in first position, for example the tool where your texts are written, or let the schedule start the scenario. A new scenario runs every 15 minutes by default, and you can change that clock on the first module. With a trigger from another app, DeepL simply translates whatever that app sends.
04What if the DeepL module you need does not exist in Make?
Use Make an API Call. The listed DeepL modules only cover translating a text, but this module can call any other part of the DeepL API from your scenario, with the same connection you already set up. You write the request yourself, so keep the DeepL API reference nearby. Note also that the Make documentation for this app is marked as AI-generated from the official DeepL documentation, so verify important details with DeepL directly before you rely on them.
05Make or n8n: which one fits DeepL better?
It depends on where the rest of your automations live. DeepL is available in both tools, as an app with 2 modules in Make and as a node in n8n. In Make, those 2 modules cover translation, and Make an API Call reaches the rest of the DeepL API. If your other processes already run in n8n, adding DeepL there keeps everything in one place. If they run in Make, stay in Make. Neither choice locks you out of the DeepL API.
Same platform

Other docs you might need on this stack.

Browse all integrations