Skip to content
Lokalise logoSupabase logo

Connect Lokalise to Supabase

Move data between Lokalise and Supabase 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
Supabase triggers
1
Supabase actions
9

Automation ideas

What you can build with Lokalise and Supabase

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

  • Key Added in Lokalise creates Upload File in Supabase

    Trigger when a new key is added to your Lokalise project

  • New Row in Supabase creates Create Comment in Lokalise

    Fires when a new row is created in a table

  • Key Added in Lokalise creates Create Row in Supabase

    Trigger when a new key is added to your Lokalise project

  • New Row in Supabase creates Create Key in Lokalise

    Fires when a new row is created in a table

  • Key Added in Lokalise creates Update Row in Supabase

    Trigger when a new key is added to your Lokalise project

  • New Row in Supabase creates Create Project in Lokalise

    Fires when a new row is created in a table

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 Supabase, 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.