When a HTTP request is received - not triggering

[DuncanIVH]

I have a Flow which uses the 'When a HTTP Request is received' trigger. This should trigger whenever an SMS is received in ClickSend.

However the Flow doesn't trigger when an SMS is received.

I have used Postman to manually test the trigger and it does work.

I have also tested from the ClickSend side of things using webhook.site. If I use the URL provided by webhook.site in the ClickSend webhook, a request is received.

The webhook in ClickSend. Adding a Test reply a request when using the webhook.site URL but not when using the Flow URL.

I have also talked to ClickSend support but obviously it's working when using webhook.site. But then Power Automate is also working when using Postman.

[abm]

Hi @DuncanIVH 

So in ClickSend you have configured the Flow HTTP url for the trigger?

Thanks

[DuncanIVH]

Hi @abm 

yes that's correct. The URL is the webhook is set as the one from the Flow trigger.

[matt-gowland]

Did you find a solution to this problem? Im having the exact same issue and have done the exact same troubleshooting steps you have. Still the http trigger is not hit.

[DuncanIVH]

@matt-gowland unfortunately not. Are you using ClickSend or a webhook from something else?

If using ClickSend I worked around it by polling ClickSend instead. For me, instant notifications wasn't important so I run the Flow once a week, poll the delivery reports and then there's an API to mark them as read at ClickSend.

[matt-gowland]

Dam. I am using a different SAAS application but same principle - trying to send a web request on an event in the SAAS app - confirmed the exact same request works using Postman, confirmed the SAAS application is sending the request exactly as expected to https://webhook.site

Ive opened a support case with Microsoft but they're generally pretty useless 🙂

Might have to resort to doing it the old fashioned way and run up a node.js endpoint to do what power automate should be able to do 😞

[Steevo]

Did anyone find a resolution?  I'm at the same place:  the request goes to webhook.site and looks good, and if I send it from Postman I get a 202 back, but never see the trigger fire in the Workflow run history. 

[nira]

Same issue here, which is frustrating when a project deadline was just moved up around eight weeks. Working fine from Postman or Nightingale with the specified response codes and -messages, but not when implemented in Azure APIM even without any authentication on either end. Just receiving a "401 - Unauthorized". Was really hoping that I had set up the connection wrongfully. Have opened a ticket with MS, but it was just moved to another team. Will post a solution here if any such thing is found.

[nira]

@DuncanIVH @Steevo @matt-gowland @abm, don't know if you all already know this as it's been a while since you interacted on this post. Sorry if it's to no use at all, but just thought you ought to know anyways. 
I've had this as a ticket with Microsoft support and it seems that if you have an APIM involved in the transaction, you'll need to set up a CORS policy with an allowed origin of https://flow.microsoft.com. This initially solved the issue for me in regards to an issue of receiving a HTTP request in an APIM, which had to be rerouted to my flow as the backend service.

[nira]

@DuncanIVH @Steevo @matt-gowland @abm If you whitelist the endpoint flow.microsoft.com you'll get the flow to run when having an APIM invoke it. That coupled with the CORS policy will do the trick.