DeepL Zapier integrationAutomate DeepL with Zapier.
The DeepL Zapier integration gives you 5 actions and 3 searches, but no trigger. Text arrives from another app, DeepL translates it, polishes it or checks it against your glossary, and the result moves on. Here is what each step does, what it costs and what breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the DeepL Zapier integration actually does
It puts DeepL in the middle of your workflows, so text gets translated or rewritten on its way from one app to another. A ticket, a form answer or a product description comes in; DeepL returns it in the target language, or in a cleaner version of the same language, ready for the next step.
Three outcomes cover most uses. Messages your team can read: Translate Text turns a customer email or a review into your working language before it lands in the helpdesk or the chat. Copy that reads better: Improve Text runs a draft through DeepL Write, so a quick note or a product blurb comes out clearer before it goes live. Terminology that stays consistent: Create Glossary, Edit Glossary and Find Glossary keep your brand names and product terms translated the same way every time.
Now the limits. DeepL has no trigger on Zapier: nothing starts when a glossary changes or a quota runs low, so another app always opens the Zap. It works on plain text only, not on files or documents. And three of the eight steps are searches, which add a step and push the Zap off the free plan. If you need more than this list, compare the DeepL n8n integration and the DeepL Make integration.
One good point: DeepL is not a premium app on Zapier, so a two-step Zap runs on the free plan.
Zapier vocabulary in one minute
Eight words you will meet in the editor. Not to be confused with a DeepL glossary, which comes later.
- Zap
- The automation you build: one starting event, then one or more steps that run each time that event happens.
- Trigger
- The event that starts the Zap. With DeepL it always comes from another app, such as a new support ticket.
- Action
- What the Zap does after it starts: here, translating, rewriting or changing a glossary in DeepL.
- Task
- The unit Zapier bills. Each action that completes successfully counts as one task on your plan.
- Polling vs instant
- A polling trigger is checked on a timer. An instant trigger is pushed by the app the moment the event happens.
- Filter
- A step that lets the Zap continue only when the data meets your condition, and stops it quietly otherwise.
- Search step
- A step that looks up something that already exists, like a glossary or your usage, for the steps that follow.
- Connection
- Your DeepL account linked to Zapier once, then reused by every DeepL step in every Zap you build.
What a DeepL Zap really costs
The trigger costs nothing. Zapier bills each action that succeeds, one task each.
- Free plan100 tasks a month
- Steps per Zap on Free2 (trigger + action)
- DeepL appNot premium
- DeepL triggersNone, start from another app
A Zap that translates a ticket and then posts it to chat uses two tasks per run. A failed action is not counted against your plan. The free plan includes 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. Add a filter, a search such as Find Glossary, or a second action, and you need a paid plan. DeepL has its own meter as well: Translate Text can return the characters counted for billing, and Check API Usage reads your usage and character limits. Zapier tasks are a separate count.
Connect DeepL to Zapier in three steps
- 01
Open the Apps page
In Zapier, go to Apps and click + Add connection. Search for DeepL in the dialog and pick it. Use the DeepL account whose usage you want these Zaps to draw on, since every translation counts there.
- 02
Sign in to DeepL
Click Add connection. DeepL opens in a new tab: sign in there. If the glossaries you need belong to a colleague's account, ask for access first, or the glossary steps will not find them.
- 03
Approve and reuse
Grant Zapier access to the account. The connection now sits on your Apps page, and every DeepL step in every Zap can select it, so you only do this once.
Your first DeepL Zap
GoalEvery form answer written in another language reaches your team chat already translated, while answers in your language skip DeepL.
- 01
Pick the starting app
Start a new Zap and choose the app where the text comes from, here a form tool. DeepL has no trigger, so the Zap always starts in another app.
- 02
Test the trigger
Run the test. Zapier fetches the three most recent submissions from the connected account, so you map the next steps on a real answer.
- 03
Add a filter
Add a Filter step that only lets through answers not written in your language. This makes the Zap multi-step, so it needs a paid plan.
- 04
Translate the text
Add Translate Text, map the answer field into the text box, and set the target language. Leave the advanced switches alone for a first run.
- 05
Send, test, publish
Add the chat step with the translation, test each step and read the output, then click Publish. Only answers submitted afterwards are handled.
DeepL actions
DeepL gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Glossary
ActionIn Zapier“Create a new glossary with custom terminology for more accurate translations”
Builds a new DeepL glossary from a list of terms and their translations, so future translations keep your vocabulary.
Delete Glossary
ActionIn Zapier“Permanently delete a glossary from your DeepL account”
Removes a glossary from your DeepL account for good. The deletion is permanent.
Edit Glossary
ActionIn Zapier“Update the name or entries of an existing glossary”
Changes the name or the entries of a glossary that already exists. You pick it from a list, so there is no ID to hunt for.
Improve Text
ActionIn Zapier“Improve or rephrase text with different writing styles and tones using DeepL Write”
Runs text through DeepL Write to rephrase it in a clearer form, with a choice of style and tone. You set the language the improvements are made in.
Translate Text
ActionIn Zapier“Translate text from one language to another using DeepL”
Sends a piece of text to DeepL and gets it back in the language you pick. Only UTF-8 plain text goes in.
DeepL searches
3 search steps look for data that already exists in DeepL, so a later step can use it.
DeepL has three search steps. They sit at the bottom of the action list, under the SEARCH heading, and three settings decide what happens when a search finds nothing or finds several matches.
Check API Usage
SearchIn Zapier“Check your DeepL API usage and character limits”
Reads how much of your DeepL allowance you have used and how much is left, against your character limit.
Find Glossary
SearchIn Zapier“Search for glossaries by ID or name”
Looks up a glossary by its name or its ID and hands it to the next step, so you do not hard-code which glossary a Zap uses.
Find Languages
SearchIn Zapier“Searches for supported languages for translation”
Returns the languages DeepL supports for translation, so a Zap can check a language before sending text.
The three settings every search exposes
- Successful if no search results are found?By default, an empty search stops the Zap and skips the steps that relied on it. Turn it on to let the Zap continue without a result.
- Create X if it doesn't exist yet?This box turns a search into find-or-create. No DeepL search offers it, so a missing glossary needs its own Create Glossary step.
- If multiple search results are found?Three choices: use the first match (the default), stop the Zap, or pass every match on at once.
When the DeepL Zap breaks
Zapier attaches no help article to DeepL, and its app page lists no DeepL-specific limit.
The failures you will meet come from how Zapier works in general and from the text you send in. The four cases below are the ones to plan for. If one already hit you, the Zapier troubleshooting guide walks through the fixes.
Earlier messages stay untranslated
A Zap only handles what happens after you publish it. Tickets or answers that arrived before stay as they are, and translating that backlog is a separate job.Rich text sent as is
Translate Text and Improve Text support UTF-8 plain text only. Clean HTML or formatted content in the step before, rather than sending it as is.A bulk import gets held back
If the starting app suddenly returns a huge batch after an import, Zapier's flood protection can pause those runs before they reach DeepL.The translation loop
A Zap that writes its translation back into the field its trigger watches starts itself again on every run, and burns through tasks fast.
Need help automating DeepL with Zapier?
A person reads every message.



