---
title: "Translate Google"
slug: "dataflow-nodes-translate"
updated: 2026-02-10T04:35:09Z
published: 2026-02-10T04:35:09Z
canonical: "docs.knovvu.com/dataflow-nodes-translate"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.knovvu.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Translate Google

A node that translates any input event with a `Text` attribute.

## Parameters

| name | description | default |
| --- | --- | --- |
| IgnoreSslErrors | Ignore any SSL certificate errors for the Http calls | false |
| SourceLanguage | Language of the source text. | tr-TR |
| TargetLanguage | Language of the target text | en-US |
| Credential | API Key Credential for the Google Translation service | empty |

## Inputs

### Audio

none

### Events

| name | description | known nodes that generate this event |
| --- | --- | --- |
| Any event that has `Data.Text` | Any Text based event such as: SR Milestone, SR Partial etc. | SR Http, SR Websocket, Translate etc. |
| [Language Change](/v1/docs/events#language-change) | Language Change events that are tagged with either "Source" or "Target" will set their respective languages. | Language Identifier, Text Language Identifier, Event Tagger |

Language Change notes

The language change event from [Language Identifier](/v1/docs/dataflow-nodes-language-identifier) and [Text Language Identifier](/v1/docs/dataflow-nodes-text-language-identifier) should be tagged using the [Event Tagger Node](/v1/docs/dataflow-nodes-event-tagger) in order to effectively change this node's language .

## Outputs

### Audio

none

### Events

| name | description |
| --- | --- |
| [Translation](/v1/docs/events#translation) | Contains the translated text in `Data.Text` field. |

## Remarks

### Requirements

The node needs a Google Translate Cloud Api key to perform. To learn more about setting up an API Key, you can refer to the [Google Cloud Translation page](https://cloud.google.com/translate/docs/setup). Keep in mind that we are utilizing the REST endpoint, and make sure you keep your API Key safe.

### Project Structure

The node expects events that have the `Text` field. Which means the node can be used with any and all SR nodes. A minimum viable project that utilizes Translate node can be built as such: ![image.png](https://cdn.document360.io/9bca2910-6a3b-4224-9470-43f91f9a6d57/Images/Documentation/image%28860%29.png)

With this project, one can use both Speech recognition and have the text translated to any desired language simultaneously.

Taking this a step further, we can construct a project such as: ![image.png](https://cdn.document360.io/9bca2910-6a3b-4224-9470-43f91f9a6d57/Images/Documentation/image%28861%29.png)

Which recognizes a speech, translates the text into another language, and uses TTS to create simultaneous audio outputs.

Keep This in Mind

Keep in mind that the [SR node](/v1/docs/dataflow-nodes-speech-recognition-sr-http) needs a model in `Source Language`, and [TTS node](/v1/docs/dataflow-nodes-tts-http) needs Voice fitting the `Target Language` in this particular case.

Finally, here's a project that manipulates the `Translation` event so that it is `punctuated, filtered, normalized` before returning the output. ![image.png](https://cdn.document360.io/9bca2910-6a3b-4224-9470-43f91f9a6d57/Images/Documentation/image%28862%29.png)

Keep This in Mind

Also, keep in mind that the [SR node](/v1/docs/dataflow-nodes-speech-recognition-sr-http) needs to fit the `Source Language`, and [Punctuation](/v1/docs/dataflow-nodes-punctuation), [Profanity Filter](/v1/docs/dataflow-nodes-profanity-filter), [Normalizer](/v1/docs/dataflow-nodes-normalizer) nodes need to fit the `Target Language`.

### Detailed Workflow

Utilizes Http calls to Google Translate Api with the provided `Api key`. Raises a `Translation` event for every response.

### Supported flow types

Stream, Batch

## Release Notes

 
     

****v4.7.0****

      
          

- Changed Node Name from "Translate" to "Translate Google"

    

  
    

****v4.6.0****

      
          

- Added Flush Support

    

****v4.2.0****

      
          

- Deprecated the **Key** field in node config;
- Added encrypted **Credential** dropdown for safer credential management.

    

****v4.1.0****

        
        

- Added SourceLanguage, TargetLanguage, SourceText fields to the event outputs.

    
    

****v3.6.0****

        
        

- Fixed a bug where responses included ampersand hash strings.

    
    

****v3.4.0****

        
        

- Introduced the ability to change source and target language during runtime with event tags.

    
    

****v1.0.0****

        
        

- Introduced node.