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.

Website CRM Integration: Bitrix24, amoCRM, Salesforce, HubSpot

A sales manager manually copies leads from email into the CRM. Half of them never make it. Follow‑up calls are missed. This isn’t a people problem — it’s an architectural gap between the website and the company’s core system. We close that gap with a direct site‑to‑CRM connection: leads land in the pipeline within 30 seconds after form submission, duplication is blocked, and status changes flow both ways automatically. Request a free integration audit to identify the bottlenecks in your current flow.

Integration isn’t just a POST to an API endpoint. It’s a battle against timeouts, duplicate records, data loss, and desynchronised states. We handle three core problems at once: asynchronous delivery (so the user never waits for the CRM), deduplication by email (one address – one lead), and two‑way feedback (a status change in the CRM instantly appears on the site). Below is how we tackle each.

Bitrix24: REST API and Event Handlers

Bitrix24 dominates the Russian B2B space. Its REST API works via OAuth 2.0 or an incoming webhook (webhook is simpler but less secure for production). Main entities are lead, deal, contact, and company.

Creating a lead requires POST /rest/crm.lead.add with the correct field set. Attaching it to a funnel means passing SOURCE_ID. Adding a timeline comment uses crm.timeline.comment.add. Real‑time tracking is done through Event Handlers: register a hook with event.bind; Bitrix24 pushes a POST to your endpoint when any deal status changes.

The real complexity lies in custom fields. Every Bitrix24 installation has its own set, and their IDs must be fetched via crm.lead.fields. Mapping those fields between the site and the CRM can be done manually or automatically — we use an automatic detection mechanism that works even in non‑standard configurations (proven on 20+ projects). We guarantee correct matching, so no lead arrives without the right pipeline stage or source tag.

amoCRM: Clean REST with Predictable Endpoints

amoCRM (now Kommo for international markets) offers a cleaner API. OAuth 2.0 with refresh token, JSON API, and well‑structured endpoints. Pipelines are pipelines, deals are leads, contacts are contacts.

A common mistake: when creating a deal you must supply pipeline_id and status_id explicitly. Without them the deal lands in the default pipeline – often the wrong one. Tags for source classification go into _embedded.tags. Incoming webhooks are configured in the admin panel; they support add, update, delete, status, and note events. We always verify the webhook signature using the API key and make sure the endpoint responds with 200 OK in under 5 seconds – otherwise the CRM marks delivery as failed.

Salesforce and HubSpot: Enterprise‑Grade Integration

Salesforce is the enterprise standard. It offers REST API, SOQL for complex queries, and Apex for server‑side logic. Integration can be direct via Salesforce REST API or through middleware like Zapier or MuleSoft. For PHP projects we use phpforce/soap-client or the Force.com‑Toolkit. The main challenge is mapping hundreds of custom objects and fields; we solve it with Describe Global to collect metadata automatically – cutting setup time by three‑quarters compared to reading documentation manually (Salesforce Developer Guide).

HubSpot is popular among SaaS companies and international B2B. Its API v3 provides a REST interface with solid SDKs for PHP and Node.js (@hubspot/api-client). Contacts, Companies, Deals are standard objects. The Forms API lets you send data from any custom form directly to HubSpot without using the native widget. One pitfall: the access_token must include the right scopes; a misconfigured token returns 403 Forbidden with a vague message. We include error_logging that captures the error code – debugging takes minutes instead of hours.

Which CRM fits your business: Bitrix24, amoCRM, or HubSpot?

Why is asynchronous sending important?

Calling a CRM API synchronously from the form handler is a mistake. The API may respond in 2 seconds – or time out. The user sits waiting. The correct pattern: form submission → save to database → queue a job → return 200 to the user immediately. A background worker then pushes the lead to the CRM. If the CRM is down, the worker retries with exponential backoff. We use Redis + Bull on Node.js or Laravel Queue on PHP – this guarantees delivery even during temporary outages.

Deduplication – how we stop duplicate leads

The same contact may fill the form twice. Without deduplication the CRM ends up with two identical leads. Before creating a new lead we search by email: for Bitrix24 we call crm.duplicate.findByComm, for HubSpot we use contacts/search. If a match is found we attach a task or comment to the existing lead instead of creating a new one. In our projects this cuts duplicate entries by 95%.

Two‑way synchronization – what happens when a manager changes a deal status

If a manager updates a deal status in the CRM, the website needs to reflect that change – especially if the client has a personal account. We configure webhooks from the CRM to an endpoint on the site, then update the local database and notify the client. Critical details: verify the webhook signature and respond with 200 OK within 5 seconds, otherwise the CRM assumes delivery failed. We guarantee that the delay between a status change in the CRM and its appearance on the site never exceeds 3 seconds.

How do we conduct integration in 5 steps?

1. Audit of data flows – analyse current lead transfer, CRM field structure, and performance bottlenecks. Deliverable: “as‑is” and “to‑be” data flow diagrams.
2. Architecture design – choose the queue mechanism (Redis Bull or Laravel Queue), define the deduplication method, and prepare a field mapping specification.
3. Implementation on staging – write code on Laravel or Node.js, configure webhooks, and test with real data: lead creation, status updates, and error handling.
4. Load testing – simulate peak traffic (e.g. 500 requests per minute) and adjust retry policies and timeout settings.
5. Deployment and documentation – push to production, train the team on monitoring and retry cleanup, and deliver full endpoint documentation.

What is included in the work

• Audit report with current data flow diagrams and typical error patterns.
• Architecture design document specifying queue, deduplication, and mapping.
• Production‑ready integration code on Laravel or Node.js.
• Webhook configuration and signature verification.
• Team training on support tasks and retry cleanup.
• 30‑day warranty support for bug fixes and mapping adjustments.

Real‑world case: real‑estate agency with 400 leads per month

Timelines

The exact cost is calculated after an audit of your current processes and CRM data structure. Contact us for a project estimate – we will send a commercial proposal within one business day. With 5+ years of experience and more than 20 completed integrations, you get a solution that works from day one. Get an engineer consultation to see how your sales funnel can run without manual lead transfer.

Additional sources: Customer relationship management (Wikipedia) · REST API (Wikipedia)