Resources · n8n integration

Google Translate n8n integrationAutomate Google Translate with n8n.

Need a translation step in the middle of a workflow? The Google Translate n8n integration adds one node with a single operation: turn a piece of text into the language you pick. Nothing here listens for events, so the workflow starts elsewhere and hands the text over.

Try the Google Translate integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Google Translate n8n integration actually do?

The Google Translate node is one of the utility nodes that ship with n8n. It carries a single resource, Language, and a single operation, Translate a language. Feed it text and a target language code, and it returns the translated string on the item, ready for whatever node comes next.

No Google Translate trigger exists in n8n, meaning no node here starts a workflow on its own, so this node always sits in the middle of a workflow instead of at its start.

Take a contact form that collects messages from a dozen countries. A Webhook node, meaning an n8n URL that the form calls on every submission, catches the entry. The Google Translate node turns the message body into English. The result lands in a channel through Slack, where the people on duty read one language and still have the original text sitting on the same item.

Content teams point the node at a spreadsheet instead. Read a column of product blurbs from Google Sheets, send each row through the translate step, write the output back beside the source. Because Translate To accepts an expression, n8n's syntax for pulling a value straight from the incoming item, the target language can come from a column rather than being fixed in the node, so one workflow covers every market on the list.

Subtitles and study material follow the same shape. A Code node splits an SRT file into lines, the translate step runs on each line, another Code node puts the file back together. Vocabulary lists work too: translate the words, pair them with the originals, mail the set to yourself with Gmail.

The node stops at translation, and that boundary is worth knowing before you build. Any Google endpoint it does not cover goes through the HTTP Request node, which reuses the same Google credential, the stored login created once in n8n and reused everywhere, through predefined authentication. One operation is a small surface, but it is also an easy one to wire.

Two details bite people. Translate To expects a language code from Google's Language Support list, not a language name typed by hand, and Text is required, so an empty field stops the execution. If output quality on one specific pair matters more than convenience, put it next to DeepL and compare on your own copy. For the platform itself, hosting and cost model included, the n8n review goes into more depth.

Connect

How do you connect Google Translate to n8n?

  1. 01

    Open the credential screen

    In n8n, go to the Credentials menu and create a Google credential, which is the stored login the node reuses in every workflow. Two methods work with Google service nodes: OAuth2, recommended because it is easier to set up, and Service Account. On n8n Cloud, certain Google nodes offer Managed OAuth2, where Sign in with Google does the whole job and the Google Cloud Console stays shut. Self-hosted instances go the custom route.

  2. 02

    Prepare the Google Cloud project

    Create a project in the Google Cloud Console, enable the APIs you need, then open APIs and Services, OAuth consent screen. Fill in App name and User support email, pick an Audience, Internal for accounts inside your Google Workspace or External for any Google account, and accept the user data policy. Under Branding, add an authorized domain: n8n.cloud on n8n Cloud, or the domain of your own instance when you self-host.

  3. 03

    Create the client and paste the keys

    Still in the console, open Credentials, then Create credentials, OAuth client ID, and choose Web application. Copy the OAuth Redirect URL shown in your n8n credential into Authorized redirect URIs, create the client, and paste the Client ID and Client Secret back into n8n. For a Service Account instead, add a JSON key, then copy client_email into Service Account Email and private_key into Private Key, without the surrounding quote marks.

Actions

What the Google Translate node can do

The Google Translate node exposes 1 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceTranslate
Language✓

Language

1 operation
01

Translate a language

language.translate

What you see in n8n

Notes & use cases

This is the whole node: it sends a string to Google Translate and returns the translated version on the item, so the next node can route, store or send it.

Key parameters

  • Text: the input text to translate. Required, and usually an expression such as {{ $json.message }} that points at a field from the node before.
  • Translate To: the target language, picked from the list or given as a language code from Google's Language Support page. It accepts an expression too, so the code can travel with the data.
Use cases
translate an inbound support message before it reaches the people who answer it, or run a column of short product descriptions into a second language for a catalog.
Need help

Need help automating Google Translate with n8n?

A person reads every message.

FAQ

Google Translate and n8n, the common questions

01Is the Google Translate n8n integration free?
On the n8n side, yes. The node ships with n8n, so there is nothing to install and nothing extra to pay for it, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both places. What a Google account costs you, or what your own translation volume implies, sits outside the node and outside this page, so check that on the Google side before you plan a large job. The node itself adds no line to your n8n bill.
02Which credentials does the Google Translate node need?
Two methods are available. OAuth2 is the recommended one, because it is more widely available and quicker to set up: on n8n Cloud, certain Google nodes support Managed OAuth2, where you click Sign in with Google and skip the console entirely. Everyone else, self-hosted users included, creates a custom OAuth2 credential with a Client ID and a Client Secret from the Google Cloud Console. Service Account is the second method, more involved, and it expects the Service Account Email and Private Key taken from the JSON key file. A credential is created once and reused across workflows.
03What are the limits of the Google Translate node in n8n?
The surface is deliberately small. One resource, Language, one operation, Translate a language, two required fields, Text and Translate To. There is no batching option in the node and no second operation to fall back on, so everything else you might want from Google on the translation side has to come from the HTTP Request node, which can call any endpoint of the API while reusing the same Google credential through predefined authentication. Plan the rest of the logic in n8n itself: a Code node to split a file, a loop over rows, an If node to skip text that is already in the right language.
04Does Google Translate have a trigger in n8n?
No. There is no Google Translate trigger node, so a workflow that uses it starts somewhere else. Three patterns cover most cases. A Schedule Trigger runs the workflow at a fixed interval, which fits a spreadsheet you translate every morning. A Webhook, an n8n URL that an outside service calls, starts the run the moment a form or an app posts data. Or another tool's trigger opens the workflow, and the translate step sits a few nodes later. Pick based on where the text arrives from, not on the node itself.
05n8n or Make for Google Translate?
It depends on what you weigh most. Make is hosted only, with no self-hosting option, and is billed per operation, which is predictable when volume is low and less so when a workflow loops over hundreds of rows. n8n runs on its own Cloud or on your servers, so the text you translate stays where you decide, and the same workflow file moves between the two without changes. Make leans more visual out of the box. For a single translate step, either works. For a pipeline that reads, loops, translates and writes back, the hosting question usually decides it.
Same platform

Other docs you might need on this stack.

Browse all integrations