Solved: Custom connector Vs Power Automate Flow

Custom connector Vs Power Automate Flow

Hello,

There is an API which I use with a Power Apps application. I authenticate (via basic authentication), retrieve an access token which expires every hour, which then needs to be passed as the bearer token in the authorization header in all subsequent requests (usual OAuth 2.0 cycle).

I have created two ways to access the API (for comparison purposes):

I have been able to call the API by using a Power Automate flow which is triggered from the Power Apps application.

I have also created a custom connector, which I use within my Power Apps app, to call the API .

Both methods enable me to make the same API requests.

Given the authentication scenario explained above, I often have to make one call to the API to authenticate/refresh the token and another call to request some data. I either do this by executing a child flow from my main Power Automate flow or, if I use the custom connector, I invoke two custom connector actions from within the app.

Bearing this in mind, is there any best practice which would recommend the use of one method over the other (custom connector or Power Automate flow)? Also, in terms of performance, is one method advised over the other one?

Thanks in advance,

Guillaume.

Categories:

Authentication

Policy Templates

Quick Links

Leaderboard > Power Apps