Skip to content
Cursor logoLokalise logo

Connect Cursor to Lokalise

Move data between Cursor and Lokalise the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Cursor triggers
5
Cursor actions
4
Lokalise triggers
3
Lokalise actions
12

Automation ideas

What you can build with Cursor and Lokalise

A few flows teams run between Cursor and Lokalise. Use one as a starting point, or build your own from scratch.

  • New Agent in Cursor creates Create Comment in Lokalise

    Triggers when a new Cursor agent is created or when agent status changes

  • Key Added in Lokalise creates Launch Agent in Cursor

    Trigger when a new key is added to your Lokalise project

  • New Agent in Cursor creates Create Key in Lokalise

    Triggers when a new Cursor agent is created or when agent status changes

  • Key Added in Lokalise creates Add Followup Instruction to Agent in Cursor

    Trigger when a new key is added to your Lokalise project

  • New Agent in Cursor creates Create Project in Lokalise

    Triggers when a new Cursor agent is created or when agent status changes

  • Key Added in Lokalise creates Find Agent Status in Cursor

    Trigger when a new key is added to your Lokalise project

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Cursor and acts in Lokalise, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.