Implementing Booking Synchronization with Google Calendar

A master spends up to 30 minutes per day manually transferring bookings to Google Calendar. Errors, duplicates, and lost records are common pain points for salons, clinics, and educational centers. Manual copying eats up to 15 hours per month — time that could be spent on clients. The integration pays for itself in a few months.

Automation with the Google Calendar API eliminates errors and duplicates. Clients get accurate schedules, and employees get free time. We implement turnkey synchronization: new bookings from the site automatically appear in the calendar, and changes from the calendar are reflected on the site. At the core are Google Calendar API v3, Google Calendar API, OAuth2, and Webhook notifications.

How does two-way synchronization with Google Calendar work?

With one-way sync, the site sends events but does not receive updates from the calendar. When a master manually moves an appointment or an admin changes the time, data diverges. Two-way sync solves this via Webhook: Google Push notifications alert our server of any changes, and we update the site's database.

Why is API sync better than manual transfer?

Manual duplication takes time and creates errors. API integration eliminates human error: an event is created seconds after booking. Two-way sync via Webhook keeps data up-to-date without master involvement. Average admin time savings — 10 hours per month.

What is included in the work?

We provide a full scope of work so you get reliable synchronization without hidden surprises.

Our team has 7+ years of experience in Google API integrations, having implemented over 50 synchronization projects for salons, clinics, and educational centers. We guarantee stable 24/7 operation — certified Google Cloud engineers ensure correct configuration of all components.

How to connect synchronization: step-by-step instructions

1. Agree on the list of masters and available calendars.
2. We configure OAuth2 authorization for each master.
3. Deploy the Webhook handler on your server.
4. Perform testing with real bookings.
5. Launch and monitor.

Google Calendar API

OAuth2 is used for authorization and Google Calendar API v3:

use Google\Client; use Google\Service\Calendar; class GoogleCalendarService { private Calendar $calendar; public function __construct(string $accessToken) { $client = new Client(); $client->setAccessToken($accessToken); $this->calendar = new Calendar($client); } public function createEvent(Booking $booking): string { $event = new Calendar\Event([ 'summary' => "📅 {$booking->service->name} — {$booking->customer_name}", 'description' => $this->buildDescription($booking), 'start' => [ 'dateTime' => $booking->starts_at->toRfc3339String(), 'timeZone' => 'Europe/Moscow', ], 'end' => [ 'dateTime' => $booking->ends_at->toRfc3339String(), 'timeZone' => 'Europe/Moscow', ], 'attendees' => [ ['email' => $booking->customer_email], ], 'reminders' => [ 'useDefault' => false, 'overrides' => [ ['method' => 'email', 'minutes' => 1440], ['method' => 'popup', 'minutes' => 60], ], ], 'extendedProperties' => [ 'private' => ['booking_id' => (string) $booking->id], ], ]); $created = $this->calendar->events->insert('primary', $event); return $created->getId(); } public function updateEvent(Booking $booking): void { $event = $this->calendar->events->get('primary', $booking->google_event_id); $event->setStart(new Calendar\EventDateTime([ 'dateTime' => $booking->starts_at->toRfc3339String(), ])); $event->setEnd(new Calendar\EventDateTime([ 'dateTime' => $booking->ends_at->toRfc3339String(), ])); $this->calendar->events->update('primary', $booking->google_event_id, $event); } public function deleteEvent(string $eventId): void { $this->calendar->events->delete('primary', $eventId); } } 

OAuth2 authorization for masters

Each master authorizes via Google and grants the application the scope https://www.googleapis.com/auth/calendar.events:

Route::get('/integrations/google-calendar/connect', function () { $client = new Google\Client(); $client->setScopes([\Google\Service\Calendar::CALENDAR_EVENTS]); $client->setState(auth()->id()); return redirect($client->createAuthUrl()); }); Route::get('/integrations/google-calendar/callback', function (Request $request) { $client = new Google\Client(); $tokens = $client->fetchAccessTokenWithAuthCode($request->code); User::find($request->state)->update([ 'google_calendar_token' => encrypt(json_encode($tokens)), ]); return redirect('/settings/integrations')->with('success', 'Google Calendar connected'); }); 

Two-way synchronization via Webhook

Google Calendar Push Notifications allow you to receive notifications about changes in the calendar:

// Subscribe to notifications $this->calendar->events->watch('primary', new Calendar\Channel([ 'id' => Str::uuid(), 'type' => 'web_hook', 'address' => 'https://example.com/webhooks/google-calendar', ])); // Notification handler Route::post('/webhooks/google-calendar', function (Request $request) { $channelId = $request->header('X-Goog-Channel-ID'); SyncGoogleCalendarChanges::dispatch($channelId); return response('ok'); }); 

Timeline and how to start

Contact us for a consultation and evaluation of your project. We will propose the optimal solution for your needs. Order a turnkey integration: one-way in 2–3 days, two-way in 4–6 days. Cost is calculated individually. Get a consultation — write to us.

Integration support and reliability

After launch, we provide support for 30 days free of charge. We monitor webhook availability, refresh OAuth2 tokens upon expiration, and promptly respond to changes in the Google Calendar API. If Google updates the notification format or introduces new rate limits — we adapt the solution at no additional cost. Accumulated experience in real projects allows us to anticipate typical failures at the development stage and minimize risks for your business. Contact us — we will help build a reliable and convenient booking automation.