How To: View All HTTP Requests Received By A Logic App Callback URI

Question

TL;DR: Is it possible to view all incoming requests to an Azure Logic App call-back URI?

I am trying to create an Azure Logic Apps workflow that responds to notifications from a 3rd party SaaS application (Zoho Bigin, in this case). I have created a basic webhook that simply responds with a HTTP 200 status code when the callback URI receives a HTTP POST request. Nothing fancy! I can test the webhook successfully using Postman.

Using their own documentation, I have configured a Notification API to send details of all changes to the Deals module ( i.e. CRUD operations). I can see that the notification is setup correct using their Notification Details endpoint.

Zoho Bigin technical support are telling me that their API is working properly but, as far as I can tell, nothing is being received by my Azure Logic App, more specifically, nothing is being triggered.

Now it is possible that they are indeed sending requests, but Azure is just ignoring them (unlikely in my opinion) but I cannot move forward until I can prove that nothing is being received at the callback URI. So, is it possible to view all incoming requests to an Azure Logic App call-back URI?

I've already setup Azure Monitoring and my Azure Logic App logs are already being shipped into it - the logs only contain run/trigger histories, not the incoming HTTP requests.

Any help/advice welcomed.

Answer 1

anonymous user If any of your applications/systems is not using the right URL i.e. HTTP Post URL that is generated by the logic app then the request will never reach to your workflow and it is not possible to trace it at your end or our end. So the only possible issue would be either the POST URL is invalid/wrong HTTP verb called or the third party has removed the query parameter which has the authentication Shared Access scheme along with other details. You can ask them to share the output response from their end when they tried to call the HTTP Post URL as the logic app should return the error and status. It would not be possible from our end to track the invalid request as there could be n number of possibilities of making the request invalid.

Only if the URL is correct with the right credentials your logic app should trigger the workflow. Then you can review the Run history details of your logic app to view the run execution of the workflow if it was Failed or Succeeded and accordingly take necessary action.