Skip to content
GitHub logoSupabase logo

Connect GitHub to Supabase

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

GitHub triggers
14
GitHub actions
19
Supabase triggers
1
Supabase actions
9

Automation ideas

What you can build with GitHub and Supabase

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

  • New Pull Request in GitHub creates Upload File in Supabase

    Triggers when there is activity on a pull request.

  • New Row in Supabase creates Create Issue in GitHub

    Fires when a new row is created in a table

  • New Pull Request in GitHub creates Create Row in Supabase

    Triggers when there is activity on a pull request.

  • New Row in Supabase creates Get issue information in GitHub

    Fires when a new row is created in a table

  • New Pull Request in GitHub creates Update Row in Supabase

    Triggers when there is activity on a pull request.

  • New Row in Supabase creates Create comment on a issue in GitHub

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