Can't trigger Power Automate flow - Web Location Connector removes port number

1

Hey all,

I have a url:
https://prod-72.westus.logic.azure.com:443/workflows/xxxxxxxxxxxxxxxxx/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=xxxxxxxxxxxxxxxxxxx

When I create the connection the port number is removed:
image

image
image838×182 7.58 KB

Any ideas where I’m going wrong?

2

Hi @Belleye and welcome to the Community!

Indicating port 443 is redundant here because it’s the default port for the HTTPS protocol that is specified in your URL.

Port 443 is hidden in URL when the protocol is HTTPS
Port 80 is hidden in URL when the protocol is HTTP.

In all other cases, a non-standard port remains. For instance, I changed port to 444 and it’s visible.

image

3

Hmmm must be getting blocks somewhere else thanks for the quick answer.

4

You’re welcome! What error are you getting?

5

401 (Unauthorized) it works fine in powershell:
Invoke-RestMethod -Method Get -Uri $url

6

In your PowerShell command you’re using GET, but in EasyMorph you’re using POST.

7

Same error on both POST and GET, I tried changing the method in Power Automate.
image

8

In the Web Location connector the authentication is set to None. Maybe there should be an authentication method (API key, OAuth or something else)?

The request is not blocked. It reaches the endpoint. Otherwise the error would’ve been either “Timed out” or “Network error” or something else.

9

We’re running 4.3.1.5
I’ll post on our internal forums and post back if I get a solution.

Thanks.

10

No problem.

One more suggestion:

Set the response type in the “Web request” action to “Return response as the action result” (see below). This will show the exact response received from PowerAutomate.

image

11

That helped and I found the error; the URL had changed from https://prod-94 to https://prod-72 :roll_eyes:

12

Very good! Did you finally manage to trigger a Power Automate workflow from EasyMorph?

PS. It could be that the URL changes when you make changes in the trigger settings in Power Automate. For instance, when you switched the accepted HTTP method from GET to POST.

13

Yep all sorted thanks