Skip to content
Jira Service Management Operations logoLokalise logo

Connect Jira Service Management Operations to Lokalise

Move data between Jira Service Management Operations 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.

Jira Service Management Operations triggers
1
Jira Service Management Operations actions
16
Lokalise triggers
3
Lokalise actions
12

Automation ideas

What you can build with Jira Service Management Operations and Lokalise

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

  • New Alert in Jira Service Management Operations creates Create Comment in Lokalise

    Triggers when a new alert is created.

  • Key Added in Lokalise creates Create Alert in Jira Service Management Operations

    Trigger when a new key is added to your Lokalise project

  • New Alert in Jira Service Management Operations creates Create Key in Lokalise

    Triggers when a new alert is created.

  • Key Added in Lokalise creates Get Alert in Jira Service Management Operations

    Trigger when a new key is added to your Lokalise project

  • New Alert in Jira Service Management Operations creates Create Project in Lokalise

    Triggers when a new alert is created.

  • Key Added in Lokalise creates Find Alerts in Jira Service Management Operations

    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 Jira Service Management Operations 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.