--- title: "Google Translate Integration" description: "Translate text between 130-plus languages, detect the source language of any text, and list supported languages using the Google Cloud Translation API." url: https://flowrunner.ai/integrations/google-translate date_modified: 2026-08-07T17:20:23-07:00 --- # Google Translate [AI](https://flowrunner.ai/integrations/category/ai-llms) Translate text between 130-plus languages, detect the source language of any text, and list supported languages using the Google Cloud Translation API. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 3 actions · API key · available [Google Translate website](https://cloud.google.com/) · [Platform Documentation](https://cloud.google.com/translate/docs) · Capability data verified 2026-07-14 1. New review posted in a non-English language 2. Agent detects the source language of the review 3. Agent translates the review into the working language 4. Agent files the translated review with the original attached 5. Analyst gets the review in a language they can read 6. A review that will be quoted publicly routes to a person to verify the wording ## What This Integration Enables Google Translate gives a flow broad, fast language coverage. It translates text between a large set of languages, detects the source language automatically so the flow does not have to know it in advance, and lists the languages it supports. For high-volume, wide-coverage translation, it is a dependable step. The reach is the point: whatever language something arrives in, the flow can read and route it. And routing is where translation becomes operational rather than a convenience. An orchestration layer detects the language, translates, and sends the message to the right place, escalating the customer-facing ones to a person. FlowRunner is built for that layer. ### Without FlowRunner **Foreign text ignored**: Non-English reviews and messages go unread **Manual translation**: Someone pastes text into a translator one message at a time **Wrong-language routing**: Messages reach agents who cannot read them ### With FlowRunner **Broad language coverage**: 130-plus languages handled in the flow **Translation automatic**: Text translates the moment it arrives **Language-aware routing**: Detection sends each message to the right person ## Use Case Scenarios ### Global Review Monitoring Reviews come in from markets around the world in many languages. The agent detects each review's language, translates it into the working language, and files it with the original. Analysts read a single stream instead of skipping the reviews they cannot understand, and nothing gets ignored for being in the wrong language. ### Inbound Message Routing Messages arrive across languages and need to reach the right agent. The agent detects the language, translates the content, and routes by topic and by which agents can handle a follow-up in that language. Messages land with the right person the first time. ### Public-Facing Content Check Content that will be published in another language passes through translation first. Routine internal text uses the machine translation directly. Anything that will appear publicly or be quoted is flagged and routed to a person to verify the wording before it ships, so broad automatic coverage never puts an unreviewed sentence in front of customers. ## Human-in-Loop Highlight Broad machine translation is ideal for reading and routing and risky for anything a customer will read verbatim. When a translation is headed for publication or a customer-facing reply on a sensitive account, FlowRunner routes it through a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step: the agent pauses, shows the original and the translation together, and sends it to a reviewer via Slack. They confirm the wording. Automatic translation covers the volume; a person checks the sentences that will be seen. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 3 actions ### Translation 1 - **Translate Text** Translates text into the target language using Google Cloud Translation (v2). Accepts a single string or an array of up to 128 strings mapped from a previous step. ### Language Detection 2 - **Detect Language** Detects the language of the provided text using Google Cloud Translation (v2). Returns the most likely ISO-639-1 language code with a confidence score between 0 and 1, plus the full list of detections. - **List Languages** Lists all languages supported by Google Cloud Translation (v2). Each entry contains the ISO-639-1 language code (used as Target Language or Source Language in Translate Text) and the language's display name, localized to the requested Names Language. ## Frequently Asked Questions ### What can FlowRunner do with Google Translate? FlowRunner agents can run Translate Text, Detect Language, and List Languages in Google Translate. ### Does connecting Google Translate to FlowRunner require OAuth? No. Google Translate connects to FlowRunner with an API key, no OAuth flow required. ### Can Google Translate trigger a FlowRunner workflow automatically? Google Translate doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Google Translate?** This integration exposes Google Translate to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/google-translate. Site index: https://flowrunner.ai/llms.txt