OtherReal-timeUpdated June 2026

Google Translate integration

Google Translate machine translation

Google Translate is the broadest-coverage machine-translation service — supports 130+ languages with consistent reliability across the long tail (where DeepL only covers ~30 languages with deeper accuracy). Tiny Command exposes two actions, no triggers: Translate Text (translate text between languages with auto-detect source), Detect Language (identify what language a text is in — returns top guesses with confidence scores). The connection uses a Google Cloud service-account key with cloudtranslate.googleapis.com.translateText permissions plus the project ID. For workflows that need translation for European-language pairs where DeepL is stronger, use DeepL. For broader language coverage (African, Asian, less common European languages) where DeepL has gaps, Google Translate. For workflows that combine many languages, Google's consistency wins; for premium quality on specific pairs, DeepL.

Connect Google Translate

No credit card required · Set up in under 2 minutes

0triggers

2actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Google Translate can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs	Open action
Detect Language	Returns the top language guesses for input text with confidence scores. Useful for "incoming message in unknown language → detect then route to the right team" or "route to right translation model based on source" workflows.	1 input	View
Translate Text	Translates text between 130+ languages. Auto-detects source if not specified. For broad language coverage where DeepL doesn't support the pair, Google is the alternative.	3 inputs	View

Recipes

Pre-built Google Translate workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Google Translate → Slack alerts

AI-triage every Google Translate event, ping the right channel only when it matters.

Google Translate → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Google Translate → Notion database

Turn Google Translate into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Google Translate once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Google Translate field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Google Translate integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Google Translate to Tiny Command?

Open the Tiny Command workflow builder, drop in a Google Translate node, and click Connect. Authorize Google Translate once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Google Translate triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Google Translate today. Use Tiny Command's universal Webhook or Schedule trigger to start Google Translate workflows, then run any Google Translate action you need.

What Google Translate actions can I run from a workflow?

2 Google Translate actions are available out of the box, covering other operations like "Detect Language". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Google Translate integration real-time?

Google Translate actions execute synchronously inside your workflow. Tiny Command waits for Google Translate's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Google Translate with Tiny Command?

No. Every Google Translate trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Google Translate API endpoint directly.

How much does the Google Translate integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Google Translate integration itself has no per-app surcharge.