Skip to main content

Product translation agent

Translates a product's name, short description and description into the languages that are still empty. You see the translation first and it is saved when you answer yes.

Runs: Embedded in Propeller · Trigger: Chat · Difficulty: Easy

What you need​

  • An n8n account. See Set up n8n.
  • An OpenAI account.
  • A Propeller API key.
  • Owner access on the Configuration role to create the agent.

How it works​

On the products page, type the SKU of a product in the agent chat. Add language codes to choose the languages, for example ABC-123 DE FR. Without codes the agent uses TARGET_LANGUAGES from Settings. The SKU has to match exactly, including capitals.

The agent reads the product's texts in the source language and translates only the texts that are empty in a target language. HTML in descriptions is kept. It shows the translation and asks whether to save it. Answer yes and exactly the shown texts are saved; answer no and nothing changes.

Existing translations are never overwritten, so the URLs of the product stay the same. A new language gets its own URL.

Install it​

  1. In n8n, import the downloaded JSON as a new workflow.
  2. On the Webhook node, set a basic auth credential (a username and password you choose) and copy the production URL.
  3. Connect your OpenAI account on the Translate node.
  4. Create a header auth credential with your Propeller API key and select it on the three GraphQL nodes.
  5. In the Settings node, set SOURCE_LANGUAGE, TARGET_LANGUAGES and LANGUAGE (of the answers: EN, the default, or NL).
  6. Activate the workflow. The agent needs an active workflow to remember a translation until you answer.
  7. Go to Admin > Agents and create an agent with Trigger Chat and Interaction Mode Multi Turn. Under Types, pick BACKOFFICE_PRODUCTS. Paste the webhook URL and the same basic auth values, and set the webhook timeout to 60000 ms: translating long descriptions can take more than the default 30 seconds. See AI Agents.
  8. Open the products page, click the Workflows button and type a SKU to test it.
Filling in your API key

In n8n, create a credential of type Header Auth and fill in its two fields exactly like this:

FieldWhat to fill in
NameapiKey
ValueYour Propeller API key

Name is not a title you pick yourself. It has to say exactly apiKey, otherwise the workflow cannot sign in. See Set up n8n for the full steps.

Placement matters

An agent type is the page where the agent appears. Stick to the types listed in the install steps: the workflow depends on the data that page sends along, so placing the agent on other pages may not work.

Make it yours​

  • Which texts: FIELDS in Settings (default name, short description and description).
  • The AI model: pick another model on the Translate node.
  • How long a translation can be saved: PROPOSAL_HOURS in Settings (default 24).

Limits​

One product per message. Products are found by their exact SKU.

Use it outside n8n​

Copy the JSON into an AI assistant and follow Adjust a workflow with an AI assistant.

Good to know

The workflows and agents in the Agent Hub are free to use and adapt. They are examples, not supported product features, so test them in a staging environment and check the results before using them in production.