Language and help

The Designer speaks your language, inside activities too: their names, their descriptions, the Properties fields, the list options and the help appear in Spanish or English. That way whoever designs understands what each field does without translating or guessing.

Change the language

Open ☰ → Tools → Settings… (or Settings, at the bottom of the rail).
On the General tab, Language section, choose the Interface language:
- System: the Windows one. If Windows is in Spanish, the Designer shows in Spanish; in any other language, in English.
- Español.
- English.

The change applies immediately: there is no need to restart the Designer or close your projects.

What changes with the language

Activities: the name, the description, the parameter groups, the help for each parameter and the card summary on the canvas.
Fields with a clear name. Each parameter shows a readable name with its unit, for example “Timeout (ms)” or “Number of clicks”, and next to it, in small print, its technical name (for example timeout), the same one stored in the playbook and shown in this documentation. Hovering over the name shows its help. Units are always stated: ms, s, min or h.
Drop-down lists: each option shows a clear text in your language.
Palette: the name of each package. Search understands both languages: you find an activity by typing its name in Spanish or in English.
Package Manager: names, descriptions and categories (AI, Data, Desktop, Documents, Mail, Queues, Human tasks…) in your language.
Documentation: each activity’s help link opens this documentation in your language.

What doesn’t change

Your projects are the same in any language. The language only changes what you see: playbooks store the technical parameter names and the list values just as always, so a project made in Spanish opens, runs and publishes the same in a Designer in English, and vice versa.

Next steps

Activity palette: find and add activities.
Parameter editors: how each kind of field is filled in.