{"id":110859,"date":"2017-06-19T12:29:05","date_gmt":"2017-06-19T19:29:05","guid":{"rendered":""},"modified":"2025-06-11T08:13:11","modified_gmt":"2025-06-11T15:13:11","slug":"automated-notification-on-new-build","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/automated-notification-on-new-build\/","title":{"rendered":"Flow of the Week: Automated notification when a new build is deployed to Production"},"content":{"rendered":"
The Microsoft Flow development team internally uses a bunch of flows that save us many person-hours, and that are interesting to showcase real-world use cases.<\/p>\n
For today, I’ll talk about a flow that we use that we use to notify our team to test the new Microsoft Flow portal build (https:\/\/flow.microsoft.com) that is going to be rolled out to all our regions. Previously, this was a manual process – internally the development leads would need to remember that a build was in the pre-production slot and remind the team to validate the bits to catch any last minute regressions. Naturally, there were lots of misses due to the human intervention this requires.<\/p>\n
We ended up creating a flow that does this quite trivially. The logic can be summed up as:<\/p>\n
A couple of interesting things to note:<\/p>\n
<\/p>\n
Querying the bits in pre-production is accomplished using the HTTP GET action against our endpoint (https:\/\/flow.microsoft.com\/healthcheck –\u00a0you can execute the same action against our endpoint, it is un-authenticated). The response is standard JSON and it contains the build version in the “x-ms-request-id” value. The results from an executed flow run (with highlighted the build version) are here:<\/p>\n
<\/p>\n
I use the ParseJSON action to parse the headers. The Use sample payload to generate schema<\/strong> is pretty handy if you don’t want to deal with schema definition (this is the easiest way I found to generate a JSON schema).<\/p>\n I use a file stored on a SharePoint site as a “state” to store the last deployed build. The file is a simple JSON with the value of the last build number as shown below. I had to create the file manually the first run to be ready.<\/p>\n
<\/p>\n
<\/p>\n