Resources · Make integration

Google Translate Make integrationAutomate Google Translate with Make.

One module is enough to make your automations speak another language. The Google Translate Make integration puts 1 module into your scenarios, the automations you build by chaining bricks like it. It fits teams that work in more than one language. Here is how to set it up.

Try the Google Translate integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Google Translate Make integration actually do?

It links your Google account to Make, then hands your scenarios one module: a brick that takes a text and turns it from one language into another. This one is a transformer, meaning it reshapes what passes through instead of fetching or storing anything. The translated text comes out and feeds whatever step you put next.

Three shapes come back over and over. The first is support: a message lands in a language nobody at the desk reads, Translate a text turns it around, and the answer leaves the same way. Then there is the catalog, where one product description is written once and the module produces the other language versions before they reach the store. Reporting is the third, a note written in one country made readable in two more without anyone opening a translation tab.

What the app does not do matters just as much. Its catalog stops at one module: no trigger to start a scenario, no action to read or write a file. The text has to arrive from somewhere else, a form, a spreadsheet, a mailbox, placed ahead of it in the flow. And the doc publishes no size or volume ceiling for this module, so none is quoted here.

The same job exists on the other side, and the question is worth asking: the n8n vs Make comparison lays out the criteria, and the Google Translate n8n integration page covers the node. On Make, this app is standard rather than Enterprise, so it runs from the Free plan, with 2 active scenarios and 15 minutes between two scheduled runs. Make pricing goes through what changes above that.

Connect

How do you connect Google Translate to Make?

  1. 01

    Get the Google side ready

    Two things are required on Google's side: an account, and billing enabled in Google Cloud Platform. If you do not have the account, create it at accounts.google.com, then sign in to the Cloud console with that same account.

  2. 02

    Create the Cloud project

    In Google Cloud Platform, create a project and configure it for Google Translate. The doc asks for this before anything happens in Make, and it is done once: every scenario that uses the module later reuses the same project.

  3. 03

    Link the account in Make

    Back in Make, add the Translate a text module to a scenario and click Create a connection. Name it, sign in with the Google account from step one, and accept the authorization window. A connection is your account linked to Make once and for all.

First scenario

Your first scenario, step by step

GoalEvery time the scenario runs, the text handed over by the module ahead of it goes through Google Translate and comes back in the language you need.

  1. 01

    Create the scenario

    Open the Scenarios page and create a new one. Make shows an empty canvas with a single + in the middle: that is where the first module goes, and the first module is always the one that brings data in.

  2. 02

    Place the module that brings the text

    Google Translate has no trigger of its own, so the opening module belongs to another app: whichever one holds the text you want translated. Search it by name, pick its module, and click Create a connection to link that account.

  3. 03

    Add Translate a text

    Click the + on the right of the first module, search Google Translate, and pick Translate a text. Make attaches it to the flow, and the output of the previous module becomes available to use inside it.

  4. 04

    Fill in the text and the two languages

    Map the text from the previous module into Translate a text, then set the language it is written in and the one you want back. The doc keeps it to that: a text, and two languages.

  5. 05

    Test with Run once

    Click Run once. Make executes the scenario one time and shows, under each module, the bundles it received: one bundle is one item passing through. Open the Google Translate module and read the text it returned.

  6. 06

    Schedule it and switch it on

    Click the clock on the first module to set the Scheduling. A new scenario runs every 15 minutes by default, which is also the floor on the Free plan. When the interval suits you, switch the scenario on.

Modules

What the module does

Google Translate gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Google Translate1

Translate a text

Transformer

In Make“Translates a text between two languages.”

Translate a text takes a piece of text and gives it back in the language you asked for, ready for the next module. Nothing is stored on the way: the text arrives, it leaves translated.

When to use it
a support ticket lands in a language nobody at the desk reads, and the reply cannot wait.
Watch out
this is the only module the app has, so files, folders and lists all belong to another app in the same scenario.
Need help

Need help automating Google Translate with Make?

A person reads every message.

FAQ

Questions that come next

01Is the Google Translate Make integration free?
Yes on the Make side: the app is standard, not reserved to the Enterprise plan, and it runs from the Free plan. What the Free plan limits is the scenario around it: 2 active scenarios, 15 minutes minimum between two scheduled runs, 5 minutes of execution, files up to 5 MB and 512 MB of transfer. Each pass through the module counts as one operation against your monthly credits. Google's own billing is settled in Google Cloud Platform and does not go through Make.
02What do you need to connect Google Translate to Make?
A Google account, and billing enabled in Google Cloud Platform. Those are the two prerequisites the doc states. On top of that you create and configure a Cloud project for Google Translate, then establish the connection from Make itself, at the moment you drop the module into a scenario. Nothing else is published: no particular plan on the app side, no extra permission to grant. Once the connection exists, every scenario you build reuses it.
03Does the trigger react in real time?
No, because this app has no trigger at all, neither scheduled nor instant. The first module of your scenario has to come from somewhere else. Two routes work. Either another app supplies the trigger, the one watching the mailbox, the form or the folder where your text appears. Or you let Make's clock set the pace: the scenario runs on the interval you choose, 15 minutes at the shortest on the Free plan and 1 minute on a paid one.
04What if the module is not enough?
You work around it, because this app carries no generic Make an API Call module to fall back on. Only the translation module exists here. When the need goes further, the usual answer is to bring a second app into the scenario: the one that reads the file, splits the list or writes the result where it belongs. The doc shows no size or volume limit on the translation itself, so there is nothing published to work around on that side. If it stalls, the team can look at the scenario with you.
05Make or n8n for Google Translate?
It depends, and not on the app: both cover Google Translate, so that alone will not settle it. What decides is everything else in the scenario, how many other apps need to fit in, who ends up maintaining it, and which editor that person already knows. Make's side of the answer is a scenario built module by module, connecting bubbles on a canvas with the mouse, no code involved. If the rest of the automation already lives in Make, adding this module there usually beats splitting the workflow across two platforms.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations