cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
bouillons
Helper V
Helper V

How to build a REST API using HTTP trigger

Hi, I've built a flow that is triggered when an HTTP request is received. My goal is to build a single point of entry to get a number of functions, instead of creating a different flow for each, for example: calling the url with relative path /getallproducts returns a list of products, /getproduct/{productid} gets the info for a single product, /searchproduct/{keyword} returns a list of products where the keyword is in the product name or description, etc... Is this at all possible with power automate ?

 

Thanks for any pointers,

Stephane

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hey there, 

 

well a custom connector is in a one to one relation with your REST API.
I think one approach in order to have only one custom connector and call different endpoints, would be to create and endpoint which works like a distributor. The endpoint accepts a json, xml or something that contains the information what to do with the additional data:

e.g.

{

  endpoint: "getproduct"

  data:{

         id:2

         }

}

Then the REST endpoint reads the json, and knows how to handle the data information. Gets the data from your datasource and gives you the information back. In such a scenario you would only need to think about the different outputs you could get from this connector. Its a bit tricky cause you would need to accept integers, strings, objects and arrays in your usecase. But I think you can handle these outputs in the parsers inside the power automate flow.

 

And to your second question? Why would you create a custom connector that can be called outside the power platform? Why wrapping your rest api in an connector and then publishing it? Why not using the REST API directly when you want to access it from the outside? Maybe I do not understand your usecase? 

Maybe you can tell me more about that?

 

With regards

Kevin

View solution in original post

4 REPLIES 4
illmatic
Helper IV
Helper IV

If you're trying to run three different functions from one request trigger, you can add parallel branches that will run simultaneously and the flow will not end until all functions have gone through.

bouillons
Helper V
Helper V

Thanks, I thought that this would get unwieldy for anything more than a couple of functions. Is it the right approach if I want to build a service with 10-50 functions ? I was hoping for an approach like when you build a custom connector, where you can just add extra actions/operations, and gradually build a complete service with a set of common objects.

 

As an alternative, is it possible to create a custom connector that can be called from outside the power platform just a standard restful API that can be called from another internal application ? 

Hey there, 

 

well a custom connector is in a one to one relation with your REST API.
I think one approach in order to have only one custom connector and call different endpoints, would be to create and endpoint which works like a distributor. The endpoint accepts a json, xml or something that contains the information what to do with the additional data:

e.g.

{

  endpoint: "getproduct"

  data:{

         id:2

         }

}

Then the REST endpoint reads the json, and knows how to handle the data information. Gets the data from your datasource and gives you the information back. In such a scenario you would only need to think about the different outputs you could get from this connector. Its a bit tricky cause you would need to accept integers, strings, objects and arrays in your usecase. But I think you can handle these outputs in the parsers inside the power automate flow.

 

And to your second question? Why would you create a custom connector that can be called outside the power platform? Why wrapping your rest api in an connector and then publishing it? Why not using the REST API directly when you want to access it from the outside? Maybe I do not understand your usecase? 

Maybe you can tell me more about that?

 

With regards

Kevin

bouillons
Helper V
Helper V

Thank you, in that case it would probably be best to bundle all product related requests in the same flow, and other topics like customers, suppliers each in their own flow. I like it because it allows to structure the different APIs and configure different security depending on the service.

 

Thanks for your time and effort Kevin,

Stephane

Helpful resources

Announcements

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (5,009)