Actions5
- Image Recognition Actions
- Speech Recognition Actions
- Text Actions
Overview
This node integrates with the Lark AI Machine Translation service to translate text from a source language to a target language using machine translation. It is useful for automating multilingual content workflows, such as translating user-generated content, documents, or messages within an automation pipeline.
Typical use cases include:
- Translating customer support tickets or chat messages automatically.
- Localizing marketing content or product descriptions.
- Enabling multilingual communication in business processes.
The node supports specifying a glossary to customize translations of specific terms and allows either using predefined input fields or sending a fully custom request body.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: "Tenant Token" or "OAuth2". |
| Glossary | A collection of term pairs to guide translation. Each item has a "from" (source term) and "to" (target term). |
| Source Language | The language code of the original text to be translated (e.g., "en" for English). |
| Target Language | The language code into which the text should be translated (e.g., "zh" for Chinese). |
| Text | The actual text string that needs to be translated. |
| Custom Body | JSON object allowing full customization of the request payload, including glossary, source_language, target_language, and text. Used if "Use Custom Body" option is enabled. |
| Options > Use Custom Body | Boolean flag to determine whether to send a custom JSON body instead of using individual parameters. |
Output
The node outputs JSON data containing the translation result. The exact structure depends on the API response but typically includes the translated text and possibly metadata about the translation.
No binary data output is indicated.
Dependencies
- Requires access to the Lark Suite Open APIs endpoint at
https://open.larksuite.com/open-apis. - Requires authentication via either a Tenant Token or OAuth2 credentials configured in n8n.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
- Authentication errors: Ensure that the correct authentication method is selected and valid credentials are provided.
- Invalid language codes: Verify that the source and target language codes conform to the expected format supported by the Lark AI translation API.
- Glossary format issues: When using glossary items, ensure each entry has both "from" and "to" strings properly defined.
- Custom Body errors: If using the custom body option, validate the JSON structure carefully to match the API requirements.
- Empty or missing text: The "Text" property must not be empty; otherwise, the API may return an error or no translation.