Google Translate
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.
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 |
|---|---|
| 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. |
| 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. |
Pre-built Google Translate workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every Google Translate event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn Google Translate into a Notion-backed source of truth, auto-tagged.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
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.
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.
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?
What Google Translate triggers does Tiny Command support?
What Google Translate actions can I run from a workflow?
Is the Google Translate integration real-time?
Do I need to write code to use Google Translate with Tiny Command?
How much does the Google Translate integration cost?
More other apps people connect.
Same category as Google Translate, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Google Translate.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
