Skip to main content
Solved

Web Hook PowerAutomate - 401 Fresh Service Error


Forum|alt.badge.img+4
  • Skilled Expert
  • 10 replies

Hi,

I'm working on creating a webhook in Power Automate to retrieve ticket details from FreshService when a specific action is performed.

I've generated the endpoint in Power Automate, and for testing purposes, I've set the permissions to "Anyone." After copying the endpoint URL into the required FreshService automation and running a test, I encountered a 401 error from FreshService. I'm unsure why this error is occurring, given that I've set the permissions to "Anyone" in Power Automate. Can anyone provide guidance on how to properly set this up?

 

Best answer by JananiPrasanthini

@KJC We’ve noticed that you're encountering a 401 error in Freshservice while testing with a Power Automate URL. Typically, a 401 error indicates that the Authorization header is either missing or incorrect. For instance, if an API request is made with a username/password, authentication will fail and trigger this error.
Since the response is coming from Power Automate, we recommend checking the tool's logs for further insights.

View original
Did this topic help you find an answer to your question?

2 replies

JananiPrasanthini
Community Debut
Forum|alt.badge.img+2

@KJC We’ve noticed that you're encountering a 401 error in Freshservice while testing with a Power Automate URL. Typically, a 401 error indicates that the Authorization header is either missing or incorrect. For instance, if an API request is made with a username/password, authentication will fail and trigger this error.
Since the response is coming from Power Automate, we recommend checking the tool's logs for further insights.


Forum|alt.badge.img+11
  • Skilled Expert
  • 93 replies
  • November 8, 2024

401 errors do typically relate to authentication issues but they can sometimes be a bit vague.

If Power Automate is not giving you the full request body output to help diagnose this error or the response from the Freshservice API is vague, you could also try submitting the same Webhook with something like Postman containing the same parameters and credentials to see if that also fails.


Reply