Open hussamkhatib opened 5 months ago
To address your concerns:
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.
To continue the conversation, mention @dosu.
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