Skip to content
PagerDuty logoSupabase logo

Connect PagerDuty to Supabase

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

PagerDuty triggers
3
PagerDuty actions
6
Supabase triggers
1
Supabase actions
9

Automation ideas

What you can build with PagerDuty and Supabase

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

  • New Incident in PagerDuty creates Upload File in Supabase

    Triggers when a new incident is created

  • New Row in Supabase creates Create Incident in PagerDuty

    Fires when a new row is created in a table

  • New Incident in PagerDuty creates Create Row in Supabase

    Triggers when a new incident is created

  • New Row in Supabase creates List Incidents in PagerDuty

    Fires when a new row is created in a table

  • New Incident in PagerDuty creates Update Row in Supabase

    Triggers when a new incident is created

  • New Row in Supabase creates Get Incident in PagerDuty

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