SPIRITTLokalise

Lokalise
Ship language-ready releases

SPIRITT maintains Lokalise keys and translations, builds language readiness dashboards, and carries approved copy into your engineering workflow. Your agent checks project languages and branch support before making changes.

SPIRITT Workspace input reading Connect me to Lokalise, with the Lokalise icon in a compact app tile.

What you can do with Lokalise.

  • Release-ready strings

    Resolve missing translations and QA flags with changes scoped to the right project and language.

  • Keys with context

    Create platform-specific keys with descriptions and constraints rather than isolated text fragments.

  • A checked handoff

    Carry reviewed translations into tested application releases and keep unresolved language work visible.

Get started in three steps.

01

Open your workspace

Start a SPIRITT workspace and describe the outcome: build a localization release gate or import new product keys.

A workspace connected to documents and knowledge
02

Connect Lokalise

Connect a personal Lokalise API token and choose a project. Writes need a read/write token; key management also requires the project permission to manage keys.

SPIRITT Workspace input reading Connect me to Lokalise, with the Lokalise icon in a compact app tile.
03

Hand over the mission

Choose the records and rules. SPIRITT carries the work through to a checked result: repair translation placeholders, with follow-through in your connected apps.

Knowledge, work items, and recurring workflow arrows

Ship language-ready releases

Questions

Lokalise, with SPIRITT.

01What can SPIRITT do with Lokalise?+
SPIRITT maintains Lokalise keys and translations, builds language readiness dashboards, and carries approved copy into your engineering workflow. Your agent checks project languages and branch support before making changes.
02How do I connect Lokalise?+
Connect a personal Lokalise API token and choose a project. Writes need a read/write token; key management also requires the project permission to manage keys.
03Can it work on release branches?+
Yes, when the project is a Software project with Branching enabled. SPIRITT discovers existing branches and targets the named branch; it does not create a branch through this connection.
04Can it update translations and review flags?+
Yes. Exact translations can be updated with text and review or status flags. Bulk key updates can also carry translations and key metadata, with permission checks appropriate to the action.
05How are large key imports handled?+
New keys are created in batches of up to 500. SPIRITT reconciles individual errors and returned IDs so partial success is not mistaken for a completed import.
06How does ongoing Lokalise work run?+
SPIRITT scans keys and translations using continuation cursors, saves release snapshots, and follows QA issues through connected tools. Team audit logs are available only with an eligible plan and team-admin token.
Buy from builders who use what they sellBuilt usingSPIRITT