MyMemory Translate tool
The MyMemory Translate tool translates untranslated block content with the MyMemory API. The provider is fixed by the tool name, so there is no provider field. MyMemory can be used anonymously; supplying an account email raises the request rate limit. A target language is required.
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 configuration 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 MyMemory
Translate untranslated blocks, supplying an account email for a higher rate limit.
email: you@example.com
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; an account email is optional and only affects the rate limit.
MyMemory makes a network round-trip per block; the anonymous tier is rate-limited.
The provider is fixed to MyMemory by the tool name and cannot be changed through configuration.
← Back to the Tool Reference