Description
I noticed a problem with the new HTTP Request trigger URLs in Power Automate. The new URLs include encoded slashes (%2F) in the trigger path, for example:
…/triggers%2Fmanual%2Fpaths/invoke?api-version=…
Behavior observed
- Works correctly when tested with Postman or curl
- Fails with a 401 Unauthorized error when used as a webhook target in ManageEngine ServiceDesk Plus
Error received:
{"error":{"code":"AuthorizationFailed","message":"You do not have permissions to perform action 'run' on scope '/triggers/manual/paths/'."}}
Workaround
If I replace %2F with a regular slash (/) in the URL, the webhook works without issues:
…/triggers/manual/paths/invoke?api-version=…
Analysis
Some systems (like Postman and curl) normalize %2F into / automatically, while others (such as ManageEngine) do not. This results in the request path being interpreted differently and causes the authorization failure.
Suggestion
- Consider generating trigger URLs with literal / instead of %2F.
- Alternatively, update the documentation to warn about this behavior and provide the workaround.
I’m sharing this here in case others run into the same issue and to suggest that Microsoft review the new URL format for better compatibility.
Thanks,
Mohammad Hadi Hikmat
