See llms.txt for all machine-readable content.

Back to Templates

Localize WordPress posts with Claude and Slack QA approvals

Created by

Created by: Gabriele || gabriele-foralosso
Gabriele

Last update

Last update 8 hours ago

Categories

Quick overview

This workflow localizes newly published WordPress posts into multiple languages using Anthropic Claude, validates translations with deterministic HTML/link/number/glossary checks plus a Claude QA review, then requests Slack approval before creating WordPress draft posts and logging results in n8n Data Tables.

How it works

  1. Runs hourly on a schedule or starts on demand from an n8n form where you provide a WordPress post URL/ID and select target languages.
  2. Loads localization settings, then reads a glossary and a localization log from n8n Data Tables to decide what to translate and avoid reprocessing.
  3. Fetches published posts from the WordPress REST API, pairs each post with each target language, and skips items that exceed the maximum content length.
  4. Sends each (post, language) to Anthropic Claude to generate a translated title, slug, excerpt, and HTML content, and retries once with specific feedback if mechanical checks fail.
  5. Runs a second Anthropic Claude request to QA the translation against the source for meaning and critical errors, then packages results into a single Slack approval message.
  6. Waits for Slack approval; if approved it creates one WordPress draft per language (prefixing failures with [REVIEW]), saves outcomes to the localization log, and posts a completion summary to Slack.

Setup

  1. Add credentials for Anthropic, Slack, and WordPress (using a user/application password that can create posts via the WordPress REST API).
  2. Create two n8n Data Tables named localization_glossary (at least: term, language, translation) and localization_log (at least: postId, language, sourceUrl, draftId, draftUrl, qaVerdict, status, localizedAt).
  3. In the localization config, set your WordPress base URL, target languages (and optional tag IDs), brand voice, lookback/max limits, and the Slack channel ID for approvals and status messages.
  4. If you use the on-demand form, ensure n8n user authentication is enabled for the form and share the form with the intended reviewers/requesters.