Lokalise
Developer ToolsConnect AI agents to Lokalise to run the full localization lifecycle. Agents create projects, define translation keys, add languages, read and update translations, upload source files, export translation bundles, and monitor localization tasks.
What This Integration Enables
Lokalise is the system of record for every string your product says in every language, and the strings in it are not just data: the translations are paid, reviewed human work. FlowRunner agents run the full localization lifecycle around that asset. They create projects and seed target languages, bulk-create and maintain translation keys, read and update individual translations with review and verification flags, upload source files whose import runs as a tracked background process, export translated bundles as downloadable ZIPs for the build pipeline, and monitor translation and review tasks for reporting. The connector's economics shape the flow design. Ferrying strings back and forth, upload on change, download on release, is pure toil and runs unattended. Destroying strings is different: Delete Key takes every language's translation of that key with it, and Delete Project takes everything. Those are proposals an agent makes, not actions it takes.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Repo to Lokalise, continuously
When source strings change in [GitHub](/integrations/github), the agent pulls the updated file, base64-encodes it, and calls Upload File against the target project with the source language set. The import runs asynchronously and the agent tracks the background process to confirm the keys landed. If the diff shows the file would touch keys whose translations were modified in Lokalise since the last sync, the agent holds the upload for the localization lead instead of letting a replace flag quietly erase translator work.
Release bundle to the build
At release cut, the agent calls Download Files with the build's format and the shipping language list, receives the temporary bundle URL, and posts it to [Slack](/integrations/slack) for the release channel, tagged to the release. Builds pick up translations from a bundle that is generated on demand, not from a folder someone remembered to refresh, and the bundle URL in the thread is the audit trail of exactly what shipped.
Coverage audit and gated cleanup
Weekly, the agent runs List Translations filtered to untranslated and unverified per language and writes the counts into a coverage report in [Google Sheets](/integrations/google-sheets), so the team sees which languages are release-ready at a glance. In the same pass it identifies keys no longer referenced by any platform, and instead of deleting them, assembles a cleanup proposal: each candidate key, its platforms, and how many languages hold translations for it. The lead approves the list before any Delete Key runs.
Human-in-Loop Highlight
Delete Key permanently deletes a translation key and every translation of it, in every language, and there is no undo. What looks like removing one stale string is actually discarding a row of paid, reviewed work across the entire language matrix. So the FlowRunner cleanup agent treats deletion as a proposal. It posts to the localization lead: "23 keys appear orphaned after the checkout refactor. Together they hold translations across all 14 project languages, including 9 keys marked reviewed. Approve deletion of the full list, keep the reviewed ones, or export a backup bundle with Download Files first?" The lead takes the backup option, the agent exports the bundle, files the URL, and only then deletes the approved keys. The work is preserved, the project is clean, and the decision belonged to the person accountable for the translation budget. That ordering is [human-in-the-loop](/concepts/human-in-the-loop) discipline applied to an asset most teams only notice once it is gone.
Agent Capabilities
17 actionsProjects
4- List Projects Enumerate the projects a token reaches, with base language and per-language statistics. The statistics feed coverage reporting.
- Get Project Load one project's settings and statistics in detail.
- Create Project Stand up a new localization project with a base language and optional seed languages, used when onboarding a new app or feature area.
- Delete Project Permanently delete a project with all keys, translations, and history. The most destructive action in the connector, and one no flow runs without explicit human direction.
Keys
5- List Keys Page through a project's keys with filters by search term, platform, and tags, with translations optionally included. The basis of audits and orphan detection.
- Create Keys Bulk-create keys with platforms, descriptions, tags, and initial translations in a single call, reporting per-key errors instead of failing wholesale.
- Get Key Load one key with its per-platform names, screenshots, and full translation set.
- Update Key Modify a key's platforms, tags, and provided translations.
- Delete Key Permanently delete a key and all of its translations. Proposed by agents, approved by people.
Translations
3- List Translations Page through translations across the project, filtered by language and by untranslated, unverified, or reviewed state. The query behind every coverage report.
- Get Translation Load one translation with its workflow flags.
- Update Translation Set new text and mark a translation reviewed or unverified as part of a QA pass.
Languages
2- List Project Languages Read the configured languages with ISO codes and plural forms.
- Add Project Languages Add new target languages that start empty across existing keys.
Files
2- Upload File Queue a localization file for asynchronous import, with the extension determining the parsed format. Options include auto-creating languages found in the file and replacing modified translations, which is exactly the switch flows gate on.
- Download Files Build an export bundle in the requested format for chosen languages and return a temporary ZIP URL, one file per language. The handoff artifact between Lokalise and the build.
Tasks
1- List Tasks Read translation and review tasks with status, languages, and progress, feeding localization status reports and notifications.
Frequently Asked Questions
What can FlowRunner do with Lokalise?
FlowRunner agents can run List Projects, Get Project, and Create Project in Lokalise, plus 14 more actions.
Does connecting Lokalise to FlowRunner require OAuth?
No. Lokalise connects to FlowRunner with an API key, no OAuth flow required.
Can Lokalise trigger a FlowRunner workflow automatically?
Lokalise doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Lokalise
$100 in credits. No card required. Connect in minutes.