Automation library · Documents and files

Star Wars language translation API for AI agents - 6 languages

Started by an event in a connected app. It calls services over plain HTTP rather than through connectors. 7 steps: small enough to read in one sitting and change without fear.

Small

7 stepsSmall: readable in one sitting
0Branches: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 1Service 6

The steps in the order they run, from what starts it.

  1. 1Translate to CheunhHttp Request ToolService
  2. 2Translate to GunganHttp Request ToolService
  3. 3Translate to HutteseHttp Request ToolService
  4. 4Translate to MandalorianHttp Request ToolService
  5. 5Translate to SithHttp Request ToolService
  6. 6Translate to YodaHttp Request ToolService
  7. 7Starwars Translations MCP ServerMcp triggerStarts it

How it's built

Starts on
An event in a connected app
Steps
7
Size
Small: readable in one sitting
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Not long. At 7 steps it can be read in one sitting and changed without fear.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 7 steps before you point it at anything that matters.