Skip to content
PagerDuty logoLokalise logo

Connect PagerDuty to Lokalise

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

PagerDuty triggers
3
PagerDuty actions
6
Lokalise triggers
3
Lokalise actions
12

Automation ideas

What you can build with PagerDuty and Lokalise

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

  • New Incident in PagerDuty creates Create Comment in Lokalise

    Triggers when a new incident is created

  • Key Added in Lokalise creates Create Incident in PagerDuty

    Trigger when a new key is added to your Lokalise project

  • New Incident in PagerDuty creates Create Key in Lokalise

    Triggers when a new incident is created

  • Key Added in Lokalise creates List Incidents in PagerDuty

    Trigger when a new key is added to your Lokalise project

  • New Incident in PagerDuty creates Create Project in Lokalise

    Triggers when a new incident is created

  • Key Added in Lokalise creates Get Incident in PagerDuty

    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 PagerDuty 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.