Yandex.Translate Make integrationAutomate Yandex.Translate with Make.
Need incoming text in another language without copying it into a translator by hand? The Yandex.Translate Make integration gives you 3 action modules: detect a language, translate a text, call the API. This page walks you from the API key to a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Yandex.Translate Make integration do for you?
The Yandex.Translate Make integration lets a Make scenario, the automation you build in Make, send text to Yandex.Translate and get back either its language or a translated version. Every step is a module, one brick of the scenario, so you drop translation into a flow that already moves your data.
Support tickets your agents can read. A ticket lands in your help desk in a language nobody on the team speaks. Determine a Text Language tells the scenario what it is, then Translate a Text writes a version your agents understand next to the original.
Product copy ready for a second market. When a new product row appears in a sheet or a database such as the one in the Airtable Make integration, the scenario passes the description to Translate a Text and saves the result in another column.
Routing by language. Some teams only need to know the language, not translate it. Determine a Text Language alone is enough to send each message to the right person or folder.
What Make does not do here: this app has no trigger, so Yandex.Translate never starts a scenario on its own. Something else starts the flow, another app or the schedule. Anything the 3 listed modules do not cover goes through Make an API Call, with the same connection. If you are weighing Make against n8n for this kind of flow, read n8n vs Make, and for the plan side see Make pricing.
How do you connect Yandex.Translate to Make?
- 01
Create an API key in Yandex
You need a Yandex account and an API key. In the management console, open the folder holding your service account, go to Identity and Access Management, then Service accounts, pick the account and click Create new key, then Create API key.
- 02
Finish and copy the key
Add a description, choose the scope the key needs and, if you like, an expiration date. Click Create and copy the key shown in the window before closing it.
- 03
Paste it into Make
In your scenario, add any Yandex.Translate module and click Create a connection. The Connection name field is optional; a clear name helps later. Paste the key and save. That connection, your Yandex account linked to Make, is reused by all 3 modules.
Your first scenario with Yandex.Translate
GoalWhen a new message reaches another app, Make detects its language with Yandex.Translate and stores a translated copy.
- 01
Create the scenario
From the Scenarios page, create a new scenario and click the +. Since Yandex.Translate has no trigger, pick the app where your text arrives first, such as your form tool or your inbox.
- 02
Add Determine a Text Language
Click the + on the right of that first module, search for Yandex.Translate and choose Determine a Text Language. Click Create a connection and paste your API key.
- 03
Map the text
In the module, map the message body from the first module. Each incoming message is a bundle, one item passed from module to module, so the check runs once per message.
- 04
Add Translate a Text
Click the next +, pick Translate a Text, reuse the same connection and map the same text. Then add the module that saves the translation where your team works.
- 05
Test with Run once
Click Run once. Make runs the scenario a single time and shows what each module received and returned, so you can read the detected language and the translation before going live.
- 06
Schedule and switch on
On the first module, set the schedule: a new scenario runs every 15 minutes by default. Then switch the scenario on. Each module run on a bundle is one operation, the unit Make counts on your plan.
What the Yandex.Translate modules do
Yandex.Translate gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Determine a Text Language
ActionIn Make“Determines a language of a given text.”
You get the language of a piece of text without reading it yourself, which is what lets a scenario decide what happens next for that message.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
This module lets you reach any endpoint of the Yandex.Translate API from your scenario, using the connection you already created, so nothing is out of reach just because it has no ready-made module.
Translate a Text
ActionIn Make“Translates a given text.”
Hand this module a text and it returns a translated version you can map into the next module: a ticket note, a sheet column, an email draft.
Need help automating Yandex.Translate with Make?
A person reads every message.
