I’ve created a Webhook to try to send event notifications to Microsoft Flow. The problem is the events never even seem to be sent out, because Flow would show me the endpoint was accessed but it hasn’t been at all. When checking the logs for the Webhook, it just shows 401. Any ideas what could be happening?
I wonder if it has something to do with the way Microsoft Flow URLs are. I’ve wrote a PHP bridge between the Webhook and Flow, and it does work, but it is of course ideally to connect them straight to each other. I had read a on a JIRA forum about replacing all instances of %2F with / in the URL and it working for them, but it had no effect when I tried it with Zoom.
We are working on your issue and will respond to you as soon as we have any updates.
Please accept my apologies for not responding in time.
I have responded to you via personal message.
I have the same issue when trying to connect webhhook to MS Flow. Can you please post possible solution? Thanks in advance.
Are you a free user? If yes, we recently made some changes that could impact you. Please see this for more details:
I have Business and Webinar license.
Please share more details like how you setup your Webhook to work with MS Flow.
What webhook events are you trying to use? What is the endpoint url?
I am trying to get information when webinar registrants are created. As an endpoint url I am using url that is automatically generated by MS Flow (my trigger step in MS Flow is Http Request Received). In the webhook logs I can see next error message - “The request has both SAS authentication scheme and ‘BEARER’ authorization scheme. Only one scheme should be used.”. After further investigation I found that Azure Logic App (and MS Flow respectively) only support SAS authentication and there is no need for Authorization header. Is there any workaround for it?
It sounds like Zoom webhooks are sending properly to your endpoint URL.
I would suggest reaching out to the Microsoft Flow team for support on how to accept webhooks with the Authorization header.
Will reach out to Microsoft. Thanks for your help.
You are welcome!
Please keep us updated!