Swagger editor for android6/29/2023 ![]() :443/workflows/ /triggers/manual/paths/invoke?api-version=&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig= In combination, the URL looks as follows with the important bits in bold… eg sig= PeZc-ljtjmJhsz00SD78YrwEohTqlUxpQuc95BQQuwU A parameter called sig with a random string value.A parameter called sv with a value of 1.0 – eg &sv=1.0.A parameter called sp with an encoded value of “/triggers/manual/run” = eg sp=%2Ftriggers%2Fmanual%2Frun.A parameter called api-version with a (at the time of writing) value of “” – eg api-version=.A URL path of “/workflows/ /triggers/manual/paths/invoke” which that identifies your specific workflow ID.If we break the URL it down, you will see: Once you have done so, it will look like this: Note that the trigger states clearly “URL will be generated after save”, so the first thing to do is generate that URL… ![]() To do so, you have to use the following trigger. Note 1: This only works for a HTTP request trigger in Flowįlow is capable of being called like any other web service. Here I will simply annotate the file with some notes that will help you customise and extend it for your own purposes. In this post I am going to assume you have watched the video and understand the intent. To save you all much pain and suffering, here is a sample file that you can use to get started. Ever since I posted a video on how to use Flow to upload photos to SharePoint from PowerApps, I get a lot of requests for help with the most mysterious bit – the swagger/openAPI file…
0 Comments
Leave a Reply. |