Skip to content
GitLab logoLokalise logo

Connect GitLab to Lokalise

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

GitLab triggers
1
GitLab actions
2
Lokalise triggers
3
Lokalise actions
12

Automation ideas

What you can build with GitLab and Lokalise

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

  • New Project Issue Event in GitLab creates Create Comment in Lokalise

    Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.

  • Key Added in Lokalise creates Create Issue in GitLab

    Trigger when a new key is added to your Lokalise project

  • New Project Issue Event in GitLab creates Create Key in Lokalise

    Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.

  • Key Added in Lokalise creates Custom API Call in GitLab

    Trigger when a new key is added to your Lokalise project

  • New Project Issue Event in GitLab creates Create Project in Lokalise

    Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.

  • Key Updated in Lokalise creates Create Issue in GitLab

    Trigger when a key is updated in 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 GitLab 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.