DeepL Translation Service

This workflow automates text translation using the DeepL API. Key nodes include Translation Request Webhook (receives POST requests), Validate Translation Request (extracts input data), Check Required Fields (validates text), Translate with DeepL (performs translation), Process Translation Result (formats output), Send Translation Response (returns results), Log Translation Request (logs details), and Send Validation Error (handles invalid inputs).\n\nSetup Requirements: Install n8n from n8n.io for local setup or sign up at cloud.n8n.io. Create a Webhook node (Translation Request Webhook) with path deepl-translation and HTTP method POST. Obtain a DeepL API key from your DeepL account (DeepL Pro > Account > API Key). In n8n’s Credentials, add HTTP Header Auth with the DeepL API key (header: Authorization, value: DeepL-Auth-Key your-api-key). Configure Translate with DeepL (https://api-free.deepl.com/v2/translate) with the credential, using form-urlencoded content type. Ensure Validate Translation Request extracts text_to_translate, target_language, source_language, formality, preserve_formatting, and split_sentences. The Check Required Fields node verifies text_to_translate is non-empty and under 50,000 characters; if invalid, Send Validation Error returns a 400 status with {"status": "error", "message": "Invalid request: text is required and must be less than 50,000 characters"}. Connect nodes in the editor. Handle errors like invalid API keys (401).\n\nTesting and Deployment: Import the JSON into n8n’s workflow editor. Test with curl -X POST http://your-n8n-instance/deepl-translation -d '{"text":"Hello, world!","target_language":"FR"}'. Verify Send Translation Response outputs status: "success", original_text, translated_text, source_language, target_language, and character_count. Check Log Translation Request for action: "deepl_translation_completed". Handle errors like missing text (400) or invalid API key (401). Activate the workflow in n8n and integrate the webhook URL into your app (e.g., translation form). Monitor logs for issues like API rate limits or unsupported target languages, ensuring reliable translation processing.