HumationHuman + Automation
Back to Catalog

Translate documents to multiple languages with Google Drive and DeepL

Daiki TakayamaDaiki Takayama
341 views
2/3/2026
SEOPuppeteerWeb ScraperOpenAIAnalysis
Official Page

Who's it for

This workflow is perfect for content creators, international teams, and businesses that need to translate documents into multiple languages automatically. Whether you're localizing documentation, translating marketing materials, or creating multilingual content, this workflow saves hours of manual work.

What it does

Automatically monitors a Google Drive folder for new documents (PDF, DOCX, TXT, or Markdown) and translates them into multiple languages using DeepL API. Each translated document is saved with a language-specific filename (e.g., document_en.pdf, document_zh.pdf) in a designated folder. You receive an email notification when all translations are complete.

How it works

  1. Monitors a Google Drive folder for new files
  2. Detects file format (PDF/DOCX/TXT/Markdown) and extracts text
  3. Translates the content into your chosen languages (default: English, Chinese, Korean, Spanish, French, German)
  4. Saves translated files with language codes in the filename
  5. Sends an email notification with translation summary
  6. Optional: Records translation history in Notion database

Set up instructions

Requirements

  • Google Drive account (for file storage)
  • DeepL API key (free tier: 500,000 characters/month)
  • Gmail account (for notifications)
  • Notion account (optional, for tracking translation history)

Setup steps

  1. Create Google Drive folders:

    • Create a "Source" folder for original files
    • Create a "Translated" folder for output
    • Copy the folder IDs from the URLs

  2. Get DeepL API key:

  3. Configure the workflow:

    • Open the "Configuration (Edit Here)" node (yellow node)
    • Replace folder IDs with your own
    • Set your notification email
    • Choose target languages

  4. Set up credentials:

    • Add Google Drive OAuth2 credentials
    • Add DeepL API credentials
    • Add Gmail OAuth2 credentials

  5. Activate the workflow and upload a test file!

Customization options

  • Change target languages: Edit the targetLanguages array in the Configuration node (supports 30+ languages)
  • Adjust polling frequency: Change trigger from "every minute" to hourly or daily for batch processing
  • Enable Notion tracking: Set enableNotion to true and provide your database ID
  • Add more file formats: Extend the Switch node to handle additional file types
  • Filter by file size: Add conditions to skip files larger than a certain size

Supported languages

EN (English), ZH (Chinese), KO (Korean), JA (Japanese), ES (Spanish), FR (French), DE (German), IT (Italian), PT (Portuguese), RU (Russian), and 20+ more.

Performance

  • Short files (1 page): ~30 seconds for 6 languages
  • Medium files (10 pages): ~2 minutes for 6 languages
  • Large files (100 pages): ~15 minutes for 6 languages

Technical Details

  • Trigger: Google Drive folder monitoring (1-minute polling)
  • Translation: DeepL API with automatic source language detection
  • Loop implementation: Split Out + Aggregate pattern for parallel translation
  • Error handling: Catches API failures and sends email alerts
  • Storage: Original file format preserved in translated outputs

Notes

  • DeepL free tier provides 500,000 characters/month (approximately 250 pages)
  • For high-volume translation, consider upgrading to DeepL Pro
  • The workflow creates new files instead of overwriting, preserving translation history
  • Google Docs are automatically converted to the appropriate format before translation

What You'll Learn

This workflow demonstrates several n8n patterns:

  • File format detection and routing (Switch node)
  • Loop implementation with Split Out + Aggregate
  • Binary data handling for file operations
  • Conditional logic with IF nodes (optional features)
  • Cross-node data references
  • Error handling and user notifications

Perfect for learning automation best practices while solving a real business problem!

Translate Documents to Multiple Languages with Google Drive and DeepL

This n8n workflow automates the translation of documents stored in Google Drive into multiple target languages using DeepL, and then notifies via Gmail and records the translation details in Notion. It's designed to streamline the process of making documents accessible to a wider, multilingual audience.

What it does

This workflow simplifies and automates the following steps:

  1. Monitors Google Drive: It triggers when new files are added to a specified Google Drive folder.
  2. Filters by File Type: It checks if the new file is a PDF document. If not, it stops the process for that file.
  3. Extracts Document Content: For PDF files, it extracts the text content from the document.
  4. Sets Translation Parameters: It defines the target languages for translation (English, German, French, Spanish, Italian, Japanese).
  5. Translates Document: It iterates through each target language and translates the extracted PDF content using DeepL.
  6. Aggregates Translations: It collects all the translated versions of the document.
  7. Writes Translated Files: It saves each translated document as a new binary file.
  8. Uploads to Google Drive: Each translated document is uploaded back to Google Drive into a specified folder.
  9. Notifies via Email: Sends an email via Gmail with details of the translation, including the original file, translated files, and target languages.
  10. Records in Notion: Creates a new item in a Notion database to log the translation event, including the original file name, translated file names, and target languages.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Account: A running n8n instance.
  • Google Drive Account: Configured with credentials in n8n to monitor a specific folder for new files and upload translated files.
  • DeepL Account: An API key or account configured in n8n for document translation.
  • Gmail Account: Configured with credentials in n8n to send email notifications.
  • Notion Account: Configured with credentials in n8n to update a database with translation logs. You will need a Notion database set up to receive the translation details.

Setup/Usage

  1. Import the workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Google Drive credentials for both the "Google Drive Trigger" and the "Google Drive" node.
    • Set up your DeepL credentials for the "DeepL" node.
    • Set up your Gmail credentials for the "Gmail" node.
    • Set up your Notion credentials for the "Notion" node.
  3. Configure Google Drive Trigger:
    • Specify the Google Drive folder ID that the workflow should monitor for new files.
  4. Configure Google Drive (Upload):
    • Specify the Google Drive folder ID where the translated documents should be uploaded.
  5. Configure Gmail:
    • Update the "To" email address, subject, and body as needed for your notification.
  6. Configure Notion:
    • Specify the Database ID for your Notion database where translation logs will be stored.
    • Ensure the Notion database has properties matching the data being sent (e.g., "Original File", "Translated Files", "Target Languages").
  7. Activate the workflow: Once all credentials and configurations are set, activate the workflow to start monitoring your Google Drive folder.

Now, whenever a new PDF document is added to your specified Google Drive folder, the workflow will automatically translate it into the configured languages, upload the translations, send an email notification, and log the event in Notion.

Related Templates

AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp

This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The “virtual executive team,” is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier 🎯 Core Features 🧑‍💼 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. 📊 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. 🕵️‍♀️ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. ⏰ 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline — key traits for early-stage success. 🗓️ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. 💬 WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. ⚙️ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. 🧩 Integrations Required Gemini API – for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API – for business and competitor analysis SerpAPI – for market research and opportunity scouting Google OAuth – to connect Sheets, Calendar, and Gmail WhatsApp Business API – for message triggers and responses 🚀 Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. 🧰 Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startup’s needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you 💡 Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business

ShadrackBy Shadrack
331

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

IT ops AI SlackBot workflow - chat with your knowledge base

Video Demo: Click here to see a video of this workflow in action. Summary Description: The "IT Department Q&A Workflow" is designed to streamline and automate the process of handling IT-related inquiries from employees through Slack. When an employee sends a direct message (DM) to the IT department's Slack channel, the workflow is triggered. The initial step involves the "Receive DMs" node, which listens for new messages. Upon receiving a message, the workflow verifies the webhook by responding to Slack's challenge request, ensuring that the communication channel is active and secure. Once the webhook is verified, the workflow checks if the message sender is a bot using the "Check if Bot" node. If the sender is identified as a bot, the workflow terminates the process to avoid unnecessary actions. If the sender is a human, the workflow sends an acknowledgment message back to the user, confirming that their query is being processed. This is achieved through the "Send Initial Message" node, which posts a simple message like "On it!" to the user's Slack channel. The core functionality of the workflow is powered by the "AI Agent" node, which utilizes the OpenAI GPT-4 model to interpret and respond to the user's query. This AI-driven node processes the text of the received message, generating an appropriate response based on the context and information available. To maintain conversation context, the "Window Buffer Memory" node stores the last five messages from each user, ensuring that the AI agent can provide coherent and contextually relevant answers. Additionally, the workflow includes a custom Knowledge Base (KB) tool (see that tool template here) that integrates with the AI agent, allowing it to search the company's internal KB for relevant information. After generating the response, the workflow cleans up the initial acknowledgment message using the "Delete Initial Message" node to keep the conversation thread clean. Finally, the generated response is sent back to the user via the "Send Message" node, providing them with the information or assistance they requested. This workflow effectively automates the IT support process, reducing response times and improving efficiency. To quickly deploy the Knowledge Ninja app in Slack, use the app manifest below and don't forget to replace the two sample urls: { "display_information": { "name": "Knowledge Ninja", "description": "IT Department Q&A Workflow", "background_color": "005e5e" }, "features": { "bot_user": { "display_name": "IT Ops AI SlackBot Workflow", "always_online": true } }, "oauth_config": { "redirect_urls": [ "Replace everything inside the double quotes with your slack redirect oauth url, for example: https://n8n.domain.com/rest/oauth2-credential/callback" ], "scopes": { "user": [ "search:read" ], "bot": [ "chat:write", "chat:write.customize", "groups:history", "groups:read", "groups:write", "groups:write.invites", "groups:write.topic", "im:history", "im:read", "im:write", "mpim:history", "mpim:read", "mpim:write", "mpim:write.topic", "usergroups:read", "usergroups:write", "users:write", "channels:history" ] } }, "settings": { "event_subscriptions": { "request_url": "Replace everything inside the double quotes with your workflow webhook url, for example: https://n8n.domain.com/webhook/99db3e73-57d8-4107-ab02-5b7e713894ad", "bot_events": [ "message.im" ] }, "orgdeployenabled": false, "socketmodeenabled": false, "tokenrotationenabled": false } }

Angel MenendezBy Angel Menendez
39013