Skip to content
PagerDuty logoSnowflake logo

Connect PagerDuty to Snowflake

Move data between PagerDuty and Snowflake 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
Snowflake triggers
5
Snowflake actions
14

Automation ideas

What you can build with PagerDuty and Snowflake

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

  • New Incident in PagerDuty creates Run Query in Snowflake

    Triggers when a new incident is created

  • New Row in Snowflake creates Create Incident in PagerDuty

    Triggers when a new row is inserted into the selected table. Uses a timestamp column you choose to detect rows added since the last check.

  • New Incident in PagerDuty creates Run Multiple Queries in Snowflake

    Triggers when a new incident is created

  • New Row in Snowflake creates List Incidents in PagerDuty

    Triggers when a new row is inserted into the selected table. Uses a timestamp column you choose to detect rows added since the last check.

  • New Incident in PagerDuty creates Insert Row in Snowflake

    Triggers when a new incident is created

  • New Row in Snowflake creates Get Incident in PagerDuty

    Triggers when a new row is inserted into the selected table. Uses a timestamp column you choose to detect rows added since the last check.

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