Skip to content
GitLab logoSupabase logo

Connect GitLab to Supabase

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

GitLab triggers
1
GitLab actions
2
Supabase triggers
1
Supabase actions
22

Automation ideas

What you can build with GitLab and Supabase

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

  • New Project Issue Event in GitLab creates Upload File in Supabase

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

  • New Row in Supabase creates Create Issue in GitLab

    Fires when a new row is created in a table

  • New Project Issue Event in GitLab creates Create Row in Supabase

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

  • New Row in Supabase creates Custom API Call in GitLab

    Fires when a new row is created in a table

  • New Project Issue Event in GitLab creates Update Row in Supabase

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

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