Overview
This node provides AI-powered translation services with cultural adaptation for text content. It is designed to translate input text from a source language (auto-detected if not specified) into a target language, optionally tailoring the translation based on audience type, industry context, region, and additional notes.
Common scenarios where this node is beneficial include:
- Translating marketing copy to different languages while adjusting tone for casual or formal audiences.
- Localizing technical documentation with industry-specific terminology.
- Adapting user interface text for specific regions or dialects.
- Quickly translating customer support messages or emails.
For example, you could use this node to translate a product description from English to Spanish, specifying a formal tone for a legal audience in Spain, ensuring the translation respects local conventions and terminology.
Properties
| Name | Meaning |
|---|---|
| Text | The text string that you want to translate. |
| Target Language | The language code to translate the text into. Options are dynamically loaded and include many common languages such as Spanish, French, German, Japanese, Chinese, etc. |
| Additional Options | A collection of optional settings to customize the translation: |
| - Target Audience | The intended audience for the translation. Options: General, Technical, Casual, Formal. |
| - Industry | The industry context to help with specialized terminology. Options: Technology, Healthcare, Finance, Education, Legal, Marketing, E-commerce. |
| - Source Language | The language code of the source text. If left empty, the source language will be auto-detected. |
| - Region | Specific region for localization (e.g., Spain, Mexico, Brazil) to adapt translations to regional variations. |
| - Translation Notes | Additional instructions or context for the translation, e.g., "Keep technical terms in English", "Use formal tone". |
Output
The node outputs JSON data containing the translation results. For the "Translate" operation on text, the output JSON includes at least the following field:
translatedText: The translated version of the input text according to the specified options.
If an error occurs during translation, the output JSON will contain an error field describing the issue.
Dependencies
- Requires an API key credential for the external AI-powered translation service.
- The node communicates with the translation API endpoint, which defaults to
https://api.i18nagent.aibut can be configured for development or custom URLs. - The node depends on n8n's HTTP request helper methods to authenticate and send requests to the translation API.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing unsupported or incorrect language codes may result in errors or fallback behavior.
- Network connectivity problems can prevent reaching the translation API.
- Exceeding API rate limits or quotas may cause request rejections.
Error messages:
- Errors returned by the API are passed through in the output under an
errorfield. - If the node fails and "Continue On Fail" is disabled, it throws an operation error indicating the item index and message.
- Errors returned by the API are passed through in the output under an
Resolutions:
- Ensure valid API credentials are configured in n8n.
- Verify language codes against supported languages.
- Check network access and proxy settings.
- Review API usage limits and upgrade plan if necessary.
Links and References
- i18n Agent API Documentation (hypothetical link)
- List of Supported Languages (API endpoint used internally)
- n8n Documentation on Creating Custom Nodes