Skip to content
Azure DevOps logoSupabase logo

Connect Azure DevOps to Supabase

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

Azure DevOps triggers
2
Azure DevOps actions
6
Supabase triggers
1
Supabase actions
22

Automation ideas

What you can build with Azure DevOps and Supabase

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

  • New or Updated Work Item (Instant) in Azure DevOps creates Upload File in Supabase

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New Row in Supabase creates Create Work Item in Azure DevOps

    Fires when a new row is created in a table

  • New or Updated Work Item (Instant) in Azure DevOps creates Create Row in Supabase

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New Row in Supabase creates Get Work Item in Azure DevOps

    Fires when a new row is created in a table

  • New or Updated Work Item (Instant) in Azure DevOps creates Update Row in Supabase

    Fires instantly when a work item is created, updated, or commented on in Azure DevOps via a Service Hooks subscription. Requires a public webhook URL reachable from Azure DevOps.

  • New Row in Supabase creates Update Work Item in Azure DevOps

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