Skip to content
Lokalise logoCloudConvert logo

Connect Lokalise to CloudConvert

Move data between Lokalise and CloudConvert 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.

Lokalise triggers
3
Lokalise actions
12
CloudConvert triggers
3
CloudConvert actions
7

Automation ideas

What you can build with Lokalise and CloudConvert

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

  • Key Added in Lokalise creates Convert File in CloudConvert

    Trigger when a new key is added to your Lokalise project

  • New Job Event in CloudConvert creates Create Comment in Lokalise

    Triggers when a new job has been created

  • Key Added in Lokalise creates Capture Website in CloudConvert

    Trigger when a new key is added to your Lokalise project

  • New Job Event in CloudConvert creates Create Key in Lokalise

    Triggers when a new job has been created

  • Key Added in Lokalise creates Merge Files to PDF in CloudConvert

    Trigger when a new key is added to your Lokalise project

  • New Job Event in CloudConvert creates Create Project in Lokalise

    Triggers when a new job has been created

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 Lokalise and acts in CloudConvert, 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.