Issue Summary

There appears to be a regression in Cal.com v6.2 when using Google Calendar together with Google Meet.

When a booking is created, the expected Google Meet URL is no longer included in the event metadata. Specifically, the videoCallUrl field inside metadata is missing.

In v6.1.16, this works correctly and the metadata contains the Meet link as expected. After upgrading to v6.2, the same flow produces an empty metadata object instead.

Expected metadata:

{
  "metadata": {
    "videoCallUrl": "https://meet.google.com/xxxxxxxxx"
  }
}

Actual metadata:

{
  "metadata": {}
}

This looks like a regression introduced in v6.2.

Steps to Reproduce

1. Set up Cal.com with Google Calendar integration enabled.
2. Configure bookings to use Google Meet as the conferencing provider.
3. Create a booking on Cal.com using v6.2.
4. Inspect the generated booking or event metadata.
5. Notice that the metadata.videoCallUrl field is missing and metadata is empty.
6. Downgrade to v6.1.16 and repeat the same test using the exact same configuration.
7. Notice that in v6.1.16 the videoCallUrl is correctly present in the metadata.

This is considered a bug because the Meet URL is expected to be exposed in the metadata when Google Meet is successfully created for the booking. The behavior changed between v6.1.16 and v6.2 without any intentional configuration change.

Actual Results

• In Cal.com v6.2, the booking or event metadata is returned as:

  {
    "metadata": {}
  }
  

• The Google Meet URL is not present in metadata.

• The issue does not occur in v6.1.16.

Expected Results

• In Cal.com v6.2, when Google Calendar + Google Meet is used, the metadata should include the Meet URL, for example:

  {
    "metadata": {
      "videoCallUrl": "https://meet.google.com/xxxxxxxxx"
    }
  }
  

• Behavior should remain consistent with v6.1.16.

Technical details

• Affected version: v6.2
• Working version: v6.1.16
• Calendar integration: Google Calendar
• Video provider: Google Meet

Anything else that may help:

• This appears to be a version regression, since the exact same setup works correctly after downgrading to v6.1.16.

Evidence

• Tested by creating bookings with the same Google Calendar + Google Meet setup on both versions.

• Result in v6.2:

  {
    "metadata": {}
  }
  

• Result in v6.1.16:

  {
    "metadata": {
      "videoCallUrl": "https://meet.google.com/xxxxxxxxx"
    }
  }
  

• The issue is reproducible and tied to the version change.