Google Translate tool
The Google Translate tool translates untranslated block content with the Google Cloud Translation API. The provider is fixed by the tool name, so there is no provider field. A target language is required and a Google API key must be supplied (resolved from the OS keychain by the CLI, or set inline); a Google Cloud project ID may also be provided.
Blocks that carry inline codes are round-tripped through semantic HTML so the API preserves the tags natively, then reconstructed from the response. With a session cache, targets already translated in a previous run are reused, so repeat runs skip blocks that are already done. When constructed without credentials the tool falls back to an offline demo provider so it remains listable and runnable for illustration.
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
apiKey | string | API key for the MT provider | |
email | string | Account email for higher rate limits (mymemory) | |
projectId | string | Google Cloud project ID (google) | |
region | string | Azure region (microsoft) | |
subscriptionKey | string | Azure subscription key (microsoft) |
Configure these parameters interactively and copy the flow-step YAML on the Tool Reference.
Examples
Translate with Google
Translate untranslated blocks using a Google Cloud API key.
apiKey: your-google-key projectId: my-gcp-project
Processing notes
Operates on translatable blocks with non-empty source; other parts pass through unchanged.
Blocks with inline codes round-trip through semantic HTML so tags survive translation.
With a session cache, already-translated targets are reused and fresh translations are cached.
Limitations
Requires a target language and a Google API key; without a key the tool runs the offline demo provider, not Google Translate.
Google makes a network round-trip per block; cost and latency scale with content volume.
The provider is fixed to Google Translate by the tool name and cannot be changed through configuration.
← Back to the Tool Reference