Automate Chinese to English translation in Google Slides with Openrouter AI
Overview of the n8n Workflow
This n8n workflow automates the translation of text in Google Slides presentations from one language to another using AI. It retrieves a specified presentation from Google Drive, extracts text from the slides, translates it in batches, and updates the presentation with the translated text. The workflow includes sticky notes with setup instructions and guidance on editable fields, formatted in Markdown for clarity.
Step-by-Step Execution of the Workflow
Here’s how the workflow operates, node by node, based on the JSON and image descriptions:
-
Manual Trigger
- Node: "When clicking ‘Execute workflow’"
- Function: Initiates the workflow when the user manually clicks "Execute workflow" in n8n.
-
Search for Google Slides Presentation
- Node: "Google Drive"
- Function: Searches Google Drive for a presentation file.
-
Retrieve Presentation Data
- Node: "Google Slides2"
- Function: Fetches the full presentation data from Google Slides.
-
Extract Text from Slides
- Node: "Code"
- Function: Extracts text from the presentation using JavaScript.
-
Split Text Array
- Node: "Split Out"
- Function: Breaks the
extractedarray into individual items.
-
Process Text in Batches
- Node: "Loop Over Items"
- Function: Loops over the text items in batches for efficient processing.
-
Translate Text with AI
- Node: "AI Agent"
- Function: Translates text from Chinese to English using an AI model.
-
Provide AI Model
- Node: "OpenRouter Chat Model"
- Function: Supplies the AI language model for the "AI Agent".
-
Replace Text in Slides
- Node: "Replace text"
- Function: Updates the Google Slides presentation with translated text.
-
Delay Between Batches
- Node: "Wait"
- Function: Adds a delay to prevent overwhelming the system.
Sticky Notes: Setup and Customization Guidance
The workflow includes three sticky notes with Markdown formatting, providing essential instructions:
How to Set Up the Workflow
To use this workflow in n8n:
- Import the JSON: Copy the provided JSON into n8n to load the workflow.
- Configure Credentials:
- Google Drive: Set up OAuth2 credentials ("Google Drive Auth") with access to the folder containing your presentation.
- Google Slides: Set up OAuth2 credentials ("Google Slides Auth") with edit permissions for the presentation.
- OpenRouter: Create an account at openrouter.ai and add the API credentials to the "OpenRouter Chat Model" node.
- Customize the Google Drive Query: Update the "Google Drive" node’s
queryStringto match your presentation’s name or ID (default is "slides"). - Test the Workflow: Click "Execute workflow" to run it manually and verify each step.
Potential Customizations
You can adapt the workflow for different needs:
- Change Language Pair:
Modify the "AI Agent" node’s system message, e.g., replace "convert all of them into English" with "convert all of them into French" to translate Chinese to French. - Use a Different AI Model:
Replace the "OpenRouter Chat Model" node with another AI provider (e.g., OpenAI) by updating the node type and credentials. - Expand Text Extraction:
Edit the "Code" node’s JavaScript to extract text from tables or other elements, not just shapes. - Adjust Batch Processing:
Change the "Loop Over Items" node’sbatchSize(e.g., to 10) or the "Wait" node’samount(e.g., to 1 second) for performance tuning. - Process Multiple Presentations:
Remove thelimit: 1in the "Google Drive" node and add a loop to handle multiple files.
Considerations and Improvements
- Error Handling: The workflow lacks explicit error handling. Add "If" nodes or error outputs to manage failures (e.g., if no presentation is found).
- Text Coverage: The "Code" node may miss text in non-shape elements (e.g., tables). Test with your presentation to confirm coverage.
- Performance: For large presentations, the 2-second wait per batch of 5 may slow things down. Adjust based on your needs and API limits.
- Permissions: Ensure your Google credentials have edit access to the presentation, or replacements will fail.
Conclusion
This n8n workflow efficiently automates the translation in Google Slides, leveraging Google Drive, Google Slides, and AI via OpenRouter. It’s well-documented with sticky notes and easy to set up with proper credentials. While robust for its purpose, it could benefit from error handling and broader text extraction. You can customize it for different languages, models, or file types by tweaking the relevant nodes as outlined.
If you have a specific question or need help with a modification, let me know! OptiLever
Automate Chinese to English Translation in Google Slides with OpenRouter AI
This n8n workflow automates the process of translating Chinese text within Google Slides presentations to English using an AI agent powered by OpenRouter. It's designed to streamline the localization of presentations, making them accessible to a broader audience without manual translation.
What it does
This workflow performs the following steps:
- Manual Trigger: The workflow is initiated manually, allowing the user to control when the translation process begins.
- Google Drive - Get File: It fetches a specified Google Slides presentation file from Google Drive.
- Google Slides - Get Presentation: It retrieves the content of the Google Slides presentation, including text from each slide.
- Code - Prepare Text for AI: A custom code node processes the retrieved slide data, extracting the Chinese text and formatting it for the AI agent. It likely identifies text boxes or specific elements containing the source language.
- Loop Over Items: The workflow iterates through each extracted text item (e.g., each Chinese text box).
- AI Agent - Translate Text: For each text item, an AI Agent (powered by OpenRouter) is invoked to translate the Chinese text to English. This agent is configured to handle translation tasks.
- Wait: A short delay is introduced after each translation, potentially to manage API rate limits or ensure proper processing.
- Code - Prepare Translated Text for Update: Another custom code node processes the translated English text, preparing it in a format suitable for updating the Google Slides presentation. This might involve mapping translated text back to its original slide and element.
- Split Out: The prepared translated text is split into individual items, ensuring each update can be handled separately.
- Google Slides - Update Text: Finally, the workflow updates the Google Slides presentation with the newly translated English text, replacing the original Chinese content.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Google Account: A Google account with access to Google Drive and Google Slides, and appropriate permissions to read and write to the target presentation.
- Google OAuth2 Credential: An n8n credential configured for Google OAuth2 to connect to Google Drive and Google Slides.
- OpenRouter API Key: An API key for OpenRouter to power the AI Agent for translation. This will require an n8n credential for OpenRouter.
Setup/Usage
- Import the workflow: Download the JSON provided and import it into your n8n instance.
- Configure Credentials:
- Set up a Google OAuth2 credential for the "Google Drive" and "Google Slides" nodes. Ensure it has access to Google Drive and Google Slides.
- Set up an OpenRouter API credential for the "OpenRouter Chat Model" node.
- Specify Google Slides File: In the "Google Drive" node, configure the "File ID" or "File Name" to point to the Google Slides presentation you wish to translate.
- Customize AI Agent (Optional): If needed, adjust the "AI Agent" node's prompt or model settings to optimize translation quality for your specific content.
- Execute the workflow: Click "Execute Workflow" to run the translation process.
The workflow will then fetch, translate, and update your Google Slides presentation with the English translations.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte