Skip to content
Azure DevOps logoLokalise logo

Connect Azure DevOps to Lokalise

Move data between Azure DevOps 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.

Azure DevOps triggers
2
Azure DevOps actions
6
Lokalise triggers
3
Lokalise actions
12

Automation ideas

What you can build with Azure DevOps and Lokalise

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

  • New or Updated Work Item (Instant) in Azure DevOps creates Create Comment in Lokalise

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • Key Added in Lokalise creates Create Work Item in Azure DevOps

    Trigger when a new key is added to your Lokalise project

  • New or Updated Work Item (Instant) in Azure DevOps creates Create Key in Lokalise

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • Key Added in Lokalise creates Get Work Item in Azure DevOps

    Trigger when a new key is added to your Lokalise project

  • New or Updated Work Item (Instant) in Azure DevOps creates Create Project in Lokalise

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • Key Added in Lokalise creates Update Work Item in Azure DevOps

    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 Azure DevOps 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.