How does the Google Calendar integration work in detail?

Google Calendar does not notify our service about changes. Our service sends requests and commands to Google Calendar and periodically polls it for updates. As a result, changes made in the Bukza calendar may not appear immediately in Google Calendar. However, we always perform a preliminary synchronization before any order is placed, ensuring that overbooking is not possible.

Only orders with time-blocking statuses are sent to Google Calendar (by default, these statuses are "Pending" and "Confirmed"). If you change any dates or statuses, we immediately send the updates to Google Calendar. We add a special property to the events we send to Google to distinguish our events from yours.

When we receive data from Google Calendar, we skip our own events to avoid duplication. Events imported from Google are not converted into actual reservations; they only block time on the calendar. If you change "non-Bukza" events in Google Calendar, these changes are also reflected in the Bukza calendar during synchronization. However, you should not modify events marked with the Bukza tag, as such changes will not affect the original reservations in our system and may be overwritten during our next synchronization.

Recurring events from Google Calendar are also taken into account—each occurrence of the series blocks the corresponding time in Bukza. We import events from Google only for the period from the beginning of the current month through the end of the next year. Events outside this period (including distant occurrences of recurring events) do not block time in Bukza.

If you want a specific Google event not to occupy time, mark it as "Free" in Google Calendar—we skip such events.

In the event title, you can add a number in square brackets. Our system will interpret this as the number of reserved shares for the resource—the Total share count of the reservation.

If the number of reserved shares is not specified, the entire resource is considered booked.