Skip to main content

Translate WordPress posts and ACF fields using DeepL and OpenAI

Workflow preview

Workflow preview
100%
Translate WordPress posts and ACF fields using DeepL and OpenAI preview
Open on n8n.io

1. Workflow Overview

Who it is for This workflow is designed for developers, content managers, and website administrators managing multilingual WordPress sites. It is highly beneficial for websites built with complex A...

Best for

  • Content Creation automation workflows
  • Multimodal AI automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.webhook, n8n-nodes-base.httprequest, n8n-nodes-base.function, n8n-nodes-base.openai, n8n-nodes-base.if, n8n-nodes-base.merge, n8n-nodes-base.code, n8n-nodes-base.itemlists

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Roger.

Original n8n.io source

1.1 Workflow description

Title
Translate WordPress posts and ACF fields using DeepL and OpenAI
Workflow name
Translate WordPress posts and ACF fields using DeepL and OpenAI

Who it is for

This workflow is designed for developers, content managers, and website administrators managing multilingual WordPress sites. It is highly beneficial for websites built with complex Advanced Custom Fields (ACF) or custom Gutenberg layouts that standard translation plugins often struggle to process efficiently.

How it works

When a post is created or updated, WordPress triggers a webhook to start the workflow. The workflow fetches the raw post JSON directly from the WordPress REST API. An OpenAI node analyzes a text snippet to detect the exact source language, ensuring it only routes and translates into missing target languages to prevent duplication. A code node then recursively extracts text from both standard fields and specific ACF fields into a single array. These strings are translated in bulk via DeepL, maintaining HTML formatting. Finally, the workflow rebuilds the original JSON structure with the translated text and pushes it back to WordPress as a newly linked translation draft.

Requirements

  • WordPress Application Password (for HTTP Basic Auth)
  • OpenAI API Key
  • DeepL API Key
  • A WordPress plugin capable of firing webhooks on post updates (e.g., WP Webhooks)

How to set up

  1. Configure the Webhook node and point your WordPress webhook plugin to the provided test/production URL.
  2. Add your HTTP Basic Auth credentials (WP Admin Username and App Password) to the WordPress request nodes.
  3. Add your OpenAI API key and DeepL API key to their respective nodes.
  4. Update the base URL in the HTTP nodes to point to your actual WordPress domain.

How to customize

Open the "Smart Router & Targets" node and update the target languages array to match your website's supported languages. Most importantly, open the "Extract Content" code node and modify the text keys array to perfectly match the field names used in your site's unique ACF configuration.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Webhook

Type / Role
n8n-nodes-base.webhook - webhook
Config choices
Version 1

Block 2 - Get Post Data

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 3

Block 3 - Prepare Text Snippet

Type / Role
n8n-nodes-base.function - function
Config choices
Version 1

Block 4 - OpenAI Language Detect

Type / Role
n8n-nodes-base.openAi - openAi
Config choices
Version 1

Block 5 - Smart Router & Targets

Type / Role
n8n-nodes-base.function - function
Config choices
Version 1

Block 6 - Needs WP Lang Fix?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 1

Block 7 - Fix WP Language Flag

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 3

Block 8 - Merge

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 2.1

Block 9 - Needs Translations?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 1

Block 10 - Extract Content

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 11 - Split by Target Lang

Type / Role
n8n-nodes-base.itemLists - itemLists
Config choices
Version 1

Block 12 - DeepL Translate

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 3

Block 13 - RECONSTRUCT JSON

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 14 - Create Translated Post

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 3

Block 15 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 17 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 18 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 19 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 20 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 21 - Sticky Note6

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Sticky Note7

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 23 - Sticky Note8

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 24 - Sticky Note9

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Translate WordPress posts and ACF fields using DeepL and OpenAI
Complexity advanced
Nodes 24
Categories Content Creation, Multimodal AI
Author Roger
Published 20 Feb 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/13543/13543.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Translate WordPress posts and ACF fields using DeepL and OpenAI do?

Who it is for This workflow is designed for developers, content managers, and website administrators managing multilingual WordPress sites. It is highly beneficial for websites built with complex A...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Content Creation, Multimodal AI use case.