You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation has mentioned general payload structure for common events like BOOKING_CREATED, BOOKING_RESHEDULED. This isn't the case for all events, for example the payload for RECORDING_READY is as show below
When does the MEETING_ENDED webhook trigger, does it trigger at the endDate of booking or when the meeting end call button is pressed.? Upon testing it looks like it is triggered upon the booking end date, but I got payload as undefined for this particular event, which again isn't documented. Is there a webhook that can be triggerred upon the end call button press ?
Is there a guide on how to test each of the webhook locally ? Right now because of the 1st 2 issues mentioned above I can't rely upon the payload structure and handle each event without testing.
Steps to Reproduce
Have webhook setup done
Book a meeting & wait for few hours so that MEETING_ENDED webhook gets triggered (Make sure to add logs to view the payload)
The payload for RECORDING_READY you've mentioned seems to be missing some fields based on the current implementation in the repository. The actual structure includes additional fields such as recording_id, end_ts, room_name, start_ts, status, max_participants, duration, and s3_key. It's important to cross-reference with the latest codebase for the most accurate structure.
The MEETING_ENDED webhook triggers at the booking's end date, not when the end call button is pressed. The issue with the payload being undefined could be due to how properties are accessed; if the base object is null, any further property access will result in undefined.
For local testing of webhook events, you can simulate webhook events by sending test requests that match the expected schema to specific endpoints, as outlined in the repository's documentation. Make sure your environment is correctly set up with the necessary variables for a successful test.
This approach should help you handle each event more reliably and test them effectively in your local environment.
About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
Is there a guide on how to test each of the webhook locally ? Right now because of the 1st 2 issues mentioned above I can't rely upon the payload structure and handle each event without testing.
you just have to set sendgrid credentials variables locally. There was also a single button "test webhook" but we had to remove it to prevent abuse/spam.
Issue Summary
undefined
for this particular event, which again isn't documented. Is there a webhook that can be triggerred upon the end call button press ?Steps to Reproduce
undefined
Evidence
From SyncLinear.com | CAL-3718
The text was updated successfully, but these errors were encountered: