401 Error on Web Request Button Power Automate

David Kortes

Hi All,

I'm starting to work with Sky Add-ins and am encountering a problem with initiating a web request trigger in power automate. When I set up the button with the encoded url from power automate I get a 401 request whenever I press it. Looking up the error it says that it could possibly be an outdated or wrong url… I tried to refresh the action and flow but nothing is working.

Looking at the documentation it doesn't tell me how to trouble shoot this! Thanks in advance for the help!

Alex Wong

@David Kortes
try this to ensure your URL is build properly

David Kortes

@Alex Wong

Unfortunately that didn't seem to do the trick. Here is the url it spit out and the error I'm getting when trying to activate.

I'm currently using the template provided by documentation just for testing purposes and in looking at other videos/ pictures it seems that my link from power automate may be missing something? There always seemed to be something after the api-version that is just not appearing for me.

Alex Wong

@David Kortes
you are definitely missing pieces of URL

for example, mine looks like this:
https://prod-31.westus.logic.azure.com:443
/workflows
/bbbbbbbbbb0000000000bbbbbbbbbb00
/triggers/manual/paths/invoke
?api-version=2016-06-01
&sp=%2Ftriggers%2Fmanual%2Frun
&sv=1.0
&sig=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

David Kortes

@Alex Wong

That is really strange… I don't know why that ending bit would be missing from my URL. Do you know of any settings that would change out the URL is generated?

I technically am still on the free trial of Power Automate… could that cause some issue?

David Kortes

@Alex Wong
I just figured it out… Apparently the trigger has been updated since documentation was created and the sample flow had the trigger set to “Any user in my tenant” instead of “Anyone." Once I changed the setting it worked right away. No video or picture had this setting present so that is how I missed it until now.

Alex Wong

@David Kortes
Yes for SKY Add-in to call the flow's URL properly, it has to be “anyone”.

That's why you need to also use “validate user identify token” right after to make sure whoever “uses” the URL is a valid user of your org.