Expose HTTP Request-Triggered Power Automate Flow in Azure API Management-Part I

N__A

Like(2)

Report

For testing purposes, I’ve created a simple HTTP-triggered workflow that receives a POST request with a JSON body containing the recipient’s mobile number and the SMS content. The workflow then sends an SMS and returns an HTTP response, as shown below:

Once we click to save this flow, the HTTP URL of the flow will be auto-generated:

Now that we have the HTTP URL, we can proceed with configuring our API Management. If you don’t already have an API management instance, follow the quick start guide to Create an Azure API Management instance

Under the APIs -> All APIs section, you will find a list of all available APIs. On the main panel, you’ll find different options for adding a new API to your list. In our case, since we’re creating one from scratch, click on ‘+Add API’ and choose ‘HTTP’ to manually define an HTTP API:

Now let’s set up the name and fill out the creation form as follows:

Display name: Provide a name for your API. For this example, let’s call it “Demo”.
Name: The “internal” name, let’s leave it as “demo”
Web service URL: copy-paste the URL we get from our flow. But we need to paste the URL until “paths” only.
API URL suffix: let’s call it ”flowdemo”

And finally, click on “Create”

Under our “Demo” API Design section, click + Add operation button. On the URL property, set the operation to POST and set the resource as “/send-sms”: