Automatic WordPress Content Translation and Google Docs Archiving - n8n Workflow

Use this powerful n8n workflow to automatically fetch WordPress blog posts, translate the content using an AI translation API, and save the localized version directly into Google Docs. Explore more n8n templates for content localization.

Workflow Preview

Ready to automate?

Download this n8n workflow template and start using it instantly.

Who is this best for?

Multilingual content creators and bloggers.
Teams needing scalable content localization solutions.
Users seeking advanced n8n templates for integrating APIs like RapidAPI.
Anyone managing WordPress sites who requires automatic translation archiving.

Overview

This robust n8n workflow template addresses the need for seamless, automated content localization. Managing a global audience requires quick translation, and this n8n automation delivers by integrating directly with your WordPress site and an external, AI-powered translation service (AI Translate Pro via RapidAPI).

The primary value of this n8n workflow is eliminating manual copy-pasting and API interaction. The data flows cleanly: WordPress content is extracted, translated instantly via the HTTP Request n8n node, and archived immediately in Google Docs for review or future use. This configuration makes it easy to rapidly generate translated versions of your source material, vastly improving efficiency for content managers looking to utilize powerful n8n features.

How it Works

The process begins with the Manual Trigger n8n trigger. Once activated, the n8n workflow immediately proceeds to the WordPress n8n node. This node is configured to retrieve a specific blog post (ID 2151) from your connected site. The fetched content, usually in HTML format, is then passed to the HTTP Request n8n node. This crucial n8n node connects to the AI translation API, sending the raw text and requesting translation into the specified language (Hindi).

The API returns the translated text, which is then handled by the final Google Docs n8n node. This n8n node takes the translated output and inserts it into a pre-defined Google Docs document, concluding the automated localization process. This entire n8n workflow structure can be easily adapted to handle dynamic post IDs or different target languages, showcasing the flexibility of n8n templates.

Installation Guide


  1. Import the n8n workflow: Copy the provided JSON and paste it into your n8n canvas using the 'New' -> 'Import from JSON' option.

  2. Set up Credentials:

WordPress: Connect your WordPress site credentials (URL, username, and password/application password).
Google Docs: Set up service account credentials for Google Docs, ensuring the service account has write access to the target document.
HTTP Request (RapidAPI): You must replace the placeholder your key in the Header Parameters with your actual x-rapidapi-key obtained from the AI Translate Pro listing on RapidAPI.

  1. Configure Nodes:

Update the WordPress n8n node to fetch a different Post ID if required.
Modify the HTTP Request n8n node's body parameters to change the target language from Hindi to your preferred localization target.
Update the Google Docs n8n node with the URL of your desired document.

Node Details

When clicking ‘Execute workflow’ (Manual Trigger)

Function: Acts as the starting n8n trigger, allowing manual execution for testing or batch runs.
Key Configuration: None (standard manual start).

Wordpress n8n node

Function: Retrieves the complete content and metadata for a specified WordPress post.
Key Configuration: Operation: Get, Post ID: 2151.

HTTP Request n8n node

Function: Sends the WordPress content to the external AI translation service via RapidAPI.
Key Configuration: URL: https://ai-translate-pro.p.rapidapi.com/translate.php, Method: POST, Content Type: multipart-form-data. Key parameters passed: text (using ={{ $json.content.rendered }}) and language (Hindi).

Google Docs n8n node

Function: Inserts the translated text received from the previous n8n node into the designated Google Docs document.
Key Configuration: Operation: Update, Text to Insert: ={{ $json.data }} (the translated response). Authentication: Service Account.

Related n8n Workflows

Free

Nodes: 5 Nodes
Updated: December 26 2025
View all
Created by
Evoort Solutions
Evoort Solutions

Featured*