Regression in v6.2 (self hosted): Google Meet videoCallUrl missing from metadata when using Google Calendar integration

[francescogatto]

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.

[Harshitazz]

I looked into this and would like to take a stab at fixing it.

From the description, this seems like a regression introduced in v6.2, possibly related to how the Google Meet response is being parsed or how metadata is being populated.

I’ll try to:

• Compare the implementation between v6.1.16 and v6.2
• Identify where videoCallUrl stopped being added to metadata
• Propose a fix to restore expected behavior

Please let me know if anyone is already working on this or if you have pointers on where this change might have been introduced.

[francescogatto]

We investigated the regression between v6.1.16 and v6.2.0 and identified two relevant commits:

5d65df9 explicitly fixes metadata propagation across the booking workflow, indicating the issue already existed during this cycle

5242e41 introduces a large booking flow change (Calendar Sync) that may have reintroduced the issue or left some paths uncovered

This suggests the problem is related to incomplete metadata propagation, particularly affecting fields like videoCallUrl.

Also, to clarify, no one from our team is currently working on this internally.

[prescottmarcus76-pixel]

Thanks for the detailed investigation! It’s helpful to see the two relevant commits identified. It definitely sounds like the issue is tied to the changes in metadata propagation and the large booking flow changes introduced in v6.2. Your plan to compare the implementations between v6.1.16 and v6.2, and pinpoint where the videoCallUrl stopped being added to metadata, seems like the right approach. If you need any additional information or assistance in testing once you propose a fix, feel free to reach out. Looking forward to the resolution!

…

On Tue, Mar 24, 2026, 4:42 AM Francesco Gatto ***@***.***> wrote: *francescogatto* left a comment (calcom/cal.com#28555) <#28555 (comment)> We investigated the regression between v6.1.16 and v6.2.0 and identified two relevant commits: 5d65df9 <5d65df9> explicitly fixes metadata propagation across the booking workflow, indicating the issue already existed during this cycle 5242e41 <5242e41> introduces a large booking flow change (Calendar Sync) that may have reintroduced the issue or left some paths uncovered This suggests the problem is related to incomplete metadata propagation, particularly affecting fields like videoCallUrl. Also, to clarify, no one from our team is currently working on this internally. — Reply to this email directly, view it on GitHub <#28555?email_source=notifications&email_token=B74QPFWV7JEIQC7S5RMIJOL4SJJ75A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJRGY3TKNBWGQ42M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4116754649>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B74QPFR3MARF2UVXPVOZDG34SJJ75AVCNFSM6AAAAACW4QTLMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMJWG42TINRUHE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>