Add "Booking Reassignment" as a Webhook Event Trigger

[angus0817]

Is your proposal related to a problem?

Currently, when setting up webhooks in Cal.com, there is no event trigger for booking reassignments (when a scheduled meeting is reassigned to another host). This creates a significant gap for users who need to sync appointment data with external platforms like CRMs, project management tools, or custom databases.

Without this webhook event, users must manually update meeting reassignments in both Cal.com and their external system, which is inefficient, prone to errors, and difficult to scale.

Describe the solution you'd like

We propose adding a new webhook event trigger specifically for booking reassignments. This would work similarly to existing webhook events, notifying external systems whenever a meeting is reassigned to a different host.

Key benefits of this feature:

• Enables real-time syncing of updated host assignments to CRMs and other external platforms.
• Reduces the need for manual updates, improving workflow efficiency.
• Enhances tracking of meeting ownership, ensuring accurate reporting and analytics.

Describe alternatives you've considered

The only current workaround is to manually track reassigned meetings and update them in both Cal.com and the external platform. Another potential solution is polling the Cal.com API for changes, but this is inefficient, resource-intensive, and not as reliable as an event-driven webhook trigger.

Additional context

This feature would be particularly useful for sales teams, support teams, and organizations that heavily rely on external integrations to manage customer interactions.

Requirement/Document

No direct external documentation, but this could be implemented similarly to other webhook triggers already available within Cal.com.

Example Mockup:

---

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