Include recurring booking uid in web request payload

[tom-avela]

Is your proposal related to a problem?

When a recurring series of bookings is cancelled, there is only 1 webhook request for the cancellation sent for a single instance of the series. There isn't any information in the payload to indicate that this was part of a series. In order to trigger some of the cancellation processes that need to run as a result of cancellations, we need to know about all of the events.

Describe the solution you'd like

Even if all of the instances can't be included in the payload, it would be very helpful to have the booking uuid of the recurring series in the webhook request payload, so that we can look up the other events via the API and process the cancellations. Another solution would be to just send a webhook request for every single instance of a recurring booking.

Describe alternatives you've considered

We could just write more code to do use the cal.com API to get more booking information for every cancellation, but that increases API chatter and complexity when just adding a single additional data point seems like it can simply quite a few things.

Additional context

None

Requirement/Document

(Share it here.)

---

House rules

• If this issue has a 🚨 needs approval label, don't start coding yet. Wait until a core member approves feature request by removing this label, then you can start coding.
  • For clarity: Non-core member issues automatically get the 🚨 needs approval label.
  • Your feature ideas are invaluable to us! However, they undergo review to ensure alignment with the product's direction.
  • Follow Best Practices lined out in our Contributor Docs

[linear]

CAL-7234