ICS UID in Booking API Response Differs from synced event in connected calendar

[robmitchell1987]

Issue Summary

We are sending our own emails as opposed to the cal.com ones and attaching our own ICS files with the meeting info. We have an issue were we're using the the ICS UID returned from the booking API which is in the format of XXX@Cal.com but when the user has connected their calendar (Google in this case) another meeting is appearing with an ICS UID in the format of XXX@google.com resulting in two meetings in the calendar which is causing confusion and results in a left over event when cancelling via our flow.

Steps to Reproduce

1. Connect Google calendar
2. Created an accepted booking
3. Inspect booking api for ICS UID
4. Download ICS from synced event and compare UID to API response

Actual Results

Two meeting invites appearing in calendar when accepted and one left over during cancellation

Expected Results

I would expect the ICS UID to be consistent so we can update the same event in their calendar through our emails

Evidence

This is tested via the booking API version 2026-02-25 and the cal.com atoms for configuring the meeting and the at version 1.8.0

[devnucleus950]

Hi, I’d like to take a look into this.

I’ll try to reproduce the issue locally and understand how the ICS UID is generated in the booking flow vs the synced calendar event.

I’ll update here with what I find.

[CyberSarvesh]

I’m trying to work on this issue. From what I can see, the problem seems to be in how we handle CreateUnifiedCalendarEventInput ,it doesn’t include an iCalUID, so that value never reaches the Google Calendar integration.

Because of that, when the event is created, Google generates its own UID, which ends up causing the mismatch and duplicate events.