Skip to content
Azure DevOps logoSnowflake logo

Connect Azure DevOps to Snowflake

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

Azure DevOps triggers
2
Azure DevOps actions
6
Snowflake triggers
5
Snowflake actions
14

Automation ideas

What you can build with Azure DevOps and Snowflake

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

  • New or Updated Work Item (Instant) in Azure DevOps creates Run Query in Snowflake

    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 Snowflake creates Create Work Item in Azure DevOps

    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 or Updated Work Item (Instant) in Azure DevOps creates Run Multiple Queries in Snowflake

    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 Snowflake creates Get Work Item in Azure DevOps

    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 or Updated Work Item (Instant) in Azure DevOps creates Insert Row in Snowflake

    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 Snowflake creates Update Work Item in Azure DevOps

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