fix(webhooks): verify requestReschedule flag in BOOKING_CANCELLED webhook#28788
Draft
jaydeep-pipaliya wants to merge 1 commit intocalcom:mainfrom
Draft
Conversation
…bhook When a host triggers 'Request Reschedule', the BOOKING_CANCELLED webhook must include requestReschedule: true so integrations can distinguish it from a permanent cancellation. Fixes calcom#28543
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fixes #28543
When a host triggers "Request Reschedule", the
BOOKING_CANCELLEDwebhook fires. This PR adds a regression test to verify that the webhook payload includesrequestReschedule: true, making it distinguishable from a permanent cancellation.Why is this needed?
Without this field being
true, webhook consumers (Zapier, n8n, Make, CRM integrations) cannot distinguish a host-requested reschedule from a genuine cancellation — causing wrong refunds, incorrect CRM status updates, and broken automations.The
requestRescheduleflag already exists in the webhook payload type (EventPayloadType) and is set inrequestReschedule.handler.ts, but there was no test asserting it was actually included in the outgoing payload.Changes
apps/web/test/handlers/requestReschedule.test.tsthat:BOOKING_CANCELLEDrequestReschedule: trueandstatus: "CANCELLED"