At-Risk Meeting Notifier not triggering

At-Risk Meeting Notifier

We have a back end that should receive a JSON whenever the At-Risk notifier webhook gets triggered (a meeting is posted on social platforms).

However we cannot get any response from the event, we tested other events to make sure our endpoint was working correctly and those other events did trigger and do give us a response.

Test cases

For all the tests the time waited was from 15-30 minutes.
The tests were deemed a failure if no HTTP Request appeared on ngrok

• Test Case 1:
• Description: Create a meeting and post it on a social media platform
• Expected results: The webhook gets invoked and a JSON with the meeting data is received.
• Actual Results: The webhook did not get invoked. Fail.

• Test Case 2:
• Description: Create a meeting and post it on different social media platforms at the same time
• Expected results: The webhook gets invoked and a JSON with the meeting data is received.
• Actual Results: The webhook did not get invoked. Fail.

• Test Case 3:
• Description: Create a meeting and post it around 5-8 times on the same social media platforms on the same account.
• Expected results: The webhook gets invoked and a JSON with the meeting data is received.
• Actual Results: The webhook did not get invoked. Fail.

• Test Case 4:
• Description: Activated the “User’s status has been updated” webhook event. Changed the presence status on our accounts.
• Expected results: The webhook gets invoked.
• Actual Results: The webhook got invoked. Pass.
In this case the Status Code is a 400 because the back-end is not fit for this type of event

• Test Case 5:
• Description: Create a meeting and post it around 5-8 times on the same social media platforms on different accounts (new and old).
• Expected results: The webhook gets invoked and a JSON with the meeting data is received.
• Actual Results: The webhook did not get invoked. Fail.

• Test Case 6:
• Description: Create a meeting and post it on social media with hashtags that could indicate the meeting is at risk. Ex.: #zoombombing, #zoommeeting.
• Expected results: The webhook gets invoked and a JSON with the meeting data is received.
• Actual Results: The webhook did not get invoked. Fail.

• Test Case 7:
• Description: Create a meeting and post it around 5-8 times on social media with hashtags.
• Expected results: The webhook gets invoked and a JSON with the meeting data is received.
• Actual Results: The webhook did not get invoked. Fail.

• Test Case 8:
• Description: Create a meeting and post it on social media, someone enters the meeting with a personal Zoom account.
• Expected results: The webhook gets invoked and a JSON with the meeting data is received.
• Actual Results: The webhook did not get invoked. Fail.

• Test Case 9:
• Description: Activated the “Create meeting” webhook event. Created a new meeting.
• Expected results: The webhook gets invoked.
• Actual Results: The webhook got invoked. Pass.

Hi @alonso.deaguinaga
Thanks for reaching out to the Zoom Developer Forum and welcome to our community!
And thanks for bringing this to our attention, please allow me some time to try and replicate this issue on my end, and will come back with an update.
Cheers,
Elisa