Unanswered

HTTP Request in Power Automate, Initiated from Power Apps

(0) Share

Report

Posted on by ginowms0405

Hello,

I'm new to the PowerApps world and have a need to push data to an application via HTTP request. I can do that by building a URL and passing it through the Launch() function. The thing is the Launch() function opens a tab when running the HTTP request. The update is clean. However, I don't want to have the user to have to close a tab. The Launch() function takes the following sample URL.

https://site.domain.com:16202/m3api-rest/execute/PPS200MI/UpdHead;cono=10;divi=001?PUNO=1017543&DWDT=20220715

When I set up the flow and perform a manual test, the URL that works perfectly in the Launch() function results in an unresolved hostname when executed from a flow. Below is a screen capture of the flow that I set up. I pass in variables from Power Apps that I use to construct the URL. I have also hardcoded in the parameters and received the same outcome during execution. I use Basic authentication.

Is there something additional that needs to be configured so that the HTTP request does not return a splash message of unresolved host name or it does not time out? I can run the URL in a browser and from within an Excel macro. However, running it from within Power Automate does not yield success. I don't know if I need to ask tech support or the application manager to check any logs to see if the connection attempt is being blocked.

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

timl 36,393 Super User 2025 Season 2 on at

Like (0)

Report

@ginowms0405

On the basis that the error message says 'unresolved host' and/or times out, it's possible that the connection attempt is being blocked and it might be useful to ask the application manager to check the logs.

I see that the target endpoint listens on port 16202 rather than the standard port 443 for SSL. So there might be something between flow and the endpoint that's blocking traffic on that port.

If there's an unauthenticated page on the target site that you access in the flow (through normal HTTP and HTTPS on port 443), that would allow you to verify that the basic connectivity works through flow.

Was this reply helpful? Yes No
ginowms0405 19 on at

Like (0)

Report

Thanks for the feedback. I pulled the configuration from an Excel spreadsheet that the application manager gave to me to mimic. It has VB code embedded in it. I've had to raise the question with some of the other IT personnel that works with the application to see if any connections are getting blocked. As I mentioned, I can send the HTTP request across by putting the URL in a browser. I think we on our end have to figure out if PowerApps is somehow not allowed a handshake.

Was this reply helpful? Yes No
ginowms0405 19 on at

Like (0)

Report

Since the HTTP approach never seemed to connect, I added a connector that execute a SQL Server stored procedure. That has worked without error and without incident. I don't know if the application blocked the connection or if there was some other factor. I did several other test API calls using the HTTP object with no joy. For now, the SQL Server stored procedure approach yields the outcome I was expecting.

Was this reply helpful? Yes No