CONTENT CREATION

Localize on CMS publish and push the variant set to regional sites

A publish webhook from your CMS fires the localization run, generates a glossary-enforced variant per region, and posts each finished variant to its regional publishing endpoint.

CategoryContent Creation
Enginesim
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCMS publish webhook receivedHTTP webhook
  • LogicValidate payload and read regions
  • ActionLocalize per region with glossaryOpenAI
  • LogicEnforce glossary, gate auto-publish
  • OutputPost each variant to its regional endpointHTTP webhook

What it does

Closes the loop from approval to live regional pages. When your CMS sends a publish webhook for an approved post, the workflow localizes the content into each region, enforces the glossary, and pushes every variant to its corresponding regional site endpoint, so going live in English automatically queues the localized rollout.

When to use it

Use it when your source content lives in a headless CMS and you want regional sites updated in lockstep with the canonical publish, without an editor manually copying content into each locale.

How it works

  1. 1The webhook trigger receives the CMS publish event with the post payload.
  2. 2A logic step validates the payload and reads the target-region list.
  3. 3An OpenAI step localizes the body per region using locale briefs and the glossary.
  4. 4A logic step enforces glossary terms and drops any variant that fails the check from auto-publish.
  5. 5An HTTP action posts each compliant variant to its regional publishing endpoint.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.