Lokalise, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Lokalise account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Project Management
- Connects with a key
- 10 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Lokalise is
Lokalise is a translation and localization management platform for managing multilingual content, projects, contributors, files, keys, translations, and localization workflows.
You paste in a key from your own Lokalise account. It is kept encrypted, and you can withdraw it from inside Lokalise whenever you like.
One message in, the work done in Lokalise.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Lokalise. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Lokalise account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Lokalise
These are the ready-made tools your AI employee already has in Lokalise. It is not limited to them, but it never has to be taught these.
- Create KeysCreate 1 to 500 keys in a Lokalise project or branch. Requires a personal read/write API token and the project's Manage keys admin right. Branch targets also require a compatible S
- Delete KeysPermanently delete one or more keys from a Lokalise project or branch. This operation is irreversible and requires a personal read/write API token with key-management permission. B
- List Audit LogsList one page of team audit events in OCSF 1.3.0 format. This endpoint requires a personal API token belonging to a team admin and a Lokalise plan that includes Audit Logs; availab
- List BranchesList one page of branches for a Lokalise project. This capability requires a Software project with Branching enabled; it is unavailable for other project types or projects with Bra
- List KeysSearch and return one cursor page of keys from a Lokalise project or branch. Translation, comment, and screenshot expansion is opt-in to keep responses small. Branch access require
- List Project LanguagesList one page of languages configured for a Lokalise project or, when branchname is supplied, for a branch. Branch access requires a compatible Software project with Branching enab
- List ProjectsList projects available to the connected Lokalise API token, optionally filtered by team or exact project names. Include settings to discover whether a Software project has Branchi
- List TranslationsSearch and return one cursor page of translations from a Lokalise project or branch by language, review state, task, or QA issue. Branch access requires a branch-enabled Software p
- Update KeysBatch update keys and their translations, including key metadata, translation content, review flags, and custom statuses, in one Lokalise project or branch. Requires a personal rea
- Update TranslationUpdate one translation's content and review or status flags in a Lokalise project or branch. Requires a personal read/write API token; a read-only token cannot perform this action.
You stay the boss of your Lokalise account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Lokalise account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Lokalise is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Lokalise and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Lokalise
- Can an AI employee really work inside Lokalise?
- Yes. It signs in to your own Lokalise account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Lokalise?
- No. Nothing moves and nothing is replaced. Your records stay in Lokalise, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Lokalise account?
- You paste in a key from your own Lokalise account. It is kept encrypted, and you can withdraw it from inside Lokalise whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Lokalise?
- It has 10 ready-made tools in Lokalise today, among them Create Keys, Delete Keys and List Audit Logs. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Lokalise and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Lokalise and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Lokalise?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Lokalise is written down with what it did and when.