Skip to content
Lokalise logoAmazon S3 logo

Connect Lokalise to Amazon S3

Move data between Lokalise and Amazon S3 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
Amazon S3 triggers
1
Amazon S3 actions
8

Automation ideas

What you can build with Lokalise and Amazon S3

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

  • Key Added in Lokalise creates Upload File in Amazon S3

    Trigger when a new key is added to your Lokalise project

  • New or Updated File in Amazon S3 creates Create Comment in Lokalise

    Triggers when you add or update a file in your bucket. The bucket/folder you choose must not contain more than 10,000 files.

  • Key Added in Lokalise creates Read File in Amazon S3

    Trigger when a new key is added to your Lokalise project

  • New or Updated File in Amazon S3 creates Create Key in Lokalise

    Triggers when you add or update a file in your bucket. The bucket/folder you choose must not contain more than 10,000 files.

  • Key Added in Lokalise creates Generate signed URL in Amazon S3

    Trigger when a new key is added to your Lokalise project

  • New or Updated File in Amazon S3 creates Create Project in Lokalise

    Triggers when you add or update a file in your bucket. The bucket/folder you choose must not contain more than 10,000 files.

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 Amazon S3, 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.