Integration · Docs and data
AI agents for Lokalise
Find Lokalise projects and their languages, list and create translation keys, read and update translations, and open translation or review tasks, with a Lokalise API token.
- Actions
- 8
- Read
- 5
- Write
- 3
Actions
What your agents can do in Lokalise
8 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 5
Look things up. Nothing changes.
List projects
Lists the Lokalise projects the token can open, as projects.
List a project's languages
Lists the languages of one project, as languages: each with lang_id, lang_iso (like en, fr_CA; what keys and tasks use), lang_name, is_rtl and plural_forms.
List keys
Lists the translation keys of a project, as keys: each with key_id, key_name.
Get a key
Reads one key by its key_id: its name per platform, description, tags, platforms, filenames, character limit, comments and every translation with its translation_id, language_iso.
List translations
Lists the translations of a project across keys, as translations: each with translation_id, key_id, language_iso, the translation text, is_reviewed, is_unverified, words and who changed it last.
Write 3
Create, change or send.
Create keys
Creates up to 100 translation keys in a software project, each with its key_name, the platforms it belongs to (ios, android, web, other), and optionally a description.
Update a translation
Replaces the text of one translation (one key in one language), found by its translation_id from List keys or List translations, and optionally marks it reviewed or unverified.
Create a task
Opens a task on some keys: a human translation or review task assigned to people per language, or an automatic_translation (AI) or lqa_by_ai task that Lokalise runs itself.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Lokalise account.
What you enter
- API token
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Lokalise data
Ask a question in plain words. The agent can list projects, list a project's languages or list keys in Lokalise, then answers with what it found.
- 02
Let an agent update Lokalise
Have the agent create keys or update a translation in Lokalise as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Lokalise and Slack: it can list projects in Lokalise and post a summary to a Slack channel in the same run.
FAQ
Lokalise and MyDeepAgents
Can MyDeepAgents connect to Lokalise?
Yes. The Lokalise connector has 8 actions: 5 read and 3 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Lokalise?
Paste an API key from your Lokalise account. You'll need: API token. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Lokalise without asking?
Only if you let it. Each of the 3 actions that change data can be set to wait for a person's approval before it runs.
Can I use Lokalise in workflows as well as agents?
Yes. Every Lokalise action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Lokalise to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.