Announcements
We have a Dataverse Custom API that works correctly from Postman or from Power Automate, but we want to use it from PowerApps, for example by pressing a button. What can we call it? Thanks.
Hi @arodeiro,
You can call a Power Automate flow in your on the press of a button. In your Power Automate flow, use the PowerApps (V1 or V2) trigger, and from there you can call your Custom API, then add a Respond to PowerApps action to return the result back to your app.
---Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.
Hi @ChrisPiasecki, thanks for the reply. We use the solution that you say in some applications with few users, but the one we are developing has more than 100 users and adding the Power Automate license doubles the monthly cost. That is why we asked for a direct solution from Power Apps or without adding a license surcharge. Thank you.
This would not require the users with a per user or flow Power Automate license. Power Apps Per app or per user license gives you entitlement for premium connectors in flow as long as its tied to the app they are using. In this case the flow has a PowerApps trigger so you are fine.
If your flows were standalone and unrelated to the app (e.g. A scheduled flow using a connector data source not used in your app) then you would require a Power Automate per user or per flow license.
Hi @ChrisPiasecki,
Thanks for the reply. I don't knew that particularity of licensing. So it seems that it is not logical to create a Dataverse Custom API to call an action, if we can use in the flow a Dataverse a step of type PerformBoundAction / PerformUnboundAction that calls the action directly, instead of publishing that action in the Dataverse Custom API. Do you agree?.
Should Dataverse Custom API be used only to connect from external applications?
Thanks.
It depends on the business logic you need to perform. If you need to write code to perform the logic, then using a custom API is good, and scales better since it doesn't carry the same overhead as a Custom Action that relies on the Workflow engine.
Custom APIs that are performing an action (POST) and not defined as a function (GET) will be available in Power Automate in the Perform a Bound/Unbound Action.
More info on this subject is detailed in this blog post.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
11manish 505
WarrenBelz 502 Most Valuable Professional
Haque 324
