The client moved the meeting by phone
Before the manager moves the event in their phone calendar and forgets the deal, so the head of sales sees yesterday's time.
After the move in the calendar reaches the deal within minutes.
A meeting planned in a Bitrix24 deal appears in the manager's Google Calendar with the client invited, and a move in the calendar comes back to the deal
The sales team keeps deals in Bitrix24, but people live in Google Calendar on their phones: that is where they see the day and where clients accept invitations. When a meeting is written in one place and moved in the other, the manager arrives at the old time or the deal shows a meeting that was cancelled. The Bitrix24 ↔ Google Calendar pair makes the deal the place where a meeting is planned and the calendar the place where it is lived: a meeting from the deal becomes a calendar event with the client as a guest, and a move, cancellation or client's reply comes back into the deal. Below: what moves, which scenarios we cover and what we rely on in both systems.
Before the manager moves the event in their phone calendar and forgets the deal, so the head of sales sees yesterday's time.
After the move in the calendar reaches the deal within minutes.
Before after planning a meeting the manager writes the client a separate letter with the time and address.
After the invitation reaches the client's calendar automatically, and the reply comes back to the deal.
Before a meeting from the CRM is put on top of a personal appointment the CRM knows nothing about.
After the planner sees the busy slots from Google Calendar before choosing the time.
For those who want to check: each point links to the official documentation page it comes from.
Ongoing REST API access in Bitrix24 Cloud is available only on paid plans in the Vibe+ lineup; the entry Essentials plan does not include API access.
Source: apidocs.bitrix24.com ↗ checked 2026-09-25Bitrix24 supports two kinds of webhooks: an inbound one that calls API methods on behalf of the employee who created it, and an outbound one that sends a Bitrix24 event to an external handler URL.
Source: apidocs.bitrix24.com ↗ checked 2026-09-25The authenticity of an outbound webhook's request is verified by comparing its application_token value against the token shown in the webhook's own settings.
Source: apidocs.bitrix24.com ↗ checked 2026-09-25An event created through the Google Calendar interface for programs appears in the calendars of all listed guests, and with the right setting each guest receives an email notification about it.
Source: developers.google.com ↗ checked 2026-09-27There is an official query that returns only busy and available periods for a set of calendars — this is what lets an assistant pick a time without seeing the events themselves.
Source: developers.google.com ↗ checked 2026-09-27A program can request only the entries that changed since its last check, which is how reschedules are picked up without re-reading the whole calendar.
Source: developers.google.com ↗ checked 2026-09-27The limits come from both systems. Bitrix24 opens its interface for integrations only on paid Vibe+ plans, so the connection is not possible on the basic Essentials plan; for a test there is a one-time 15-day trial. Bitrix24 also limits the request rate and blocks requests above the threshold for a while, so a mass transfer of old meetings is done in portions. Google Calendar sends invitations only to guests with a real email, so a contact without an email gets the meeting in the deal but no invitation.
Three steps from a first message to work on your project.
Describe the task in the form — in text or by voice. Budget and timing are optional.
A developer studies the brief, asks about anything unclear and sends an estimate.
Once scope and price are agreed, the work begins.
or write to info@coreviaflow.space
Describe the task in text or a voice message. We look at your setup and reply with a plan.
Four services people come to us for most often. Each page explains what we do, how the work goes and where to start.
Choose the system, set up the pipeline, migrate data, train the team.
Learn more →Accounting, telephony, website, payments and messengers feed the CRM on their own.
Learn more →Orders, requests and answers around the clock, straight into your CRM.
Learn more →Flows between CRM, email, spreadsheets, payments and AI, on your own server.
Learn more →Deals, calls and documents move through Bitrix24 on their own, tracked step by step
See scenarios →A meeting booked in your CRM lands in the manager's Google Calendar with an invitation to the client — and a change in the calendar goes straight back to the CRM
See scenarios →Meetings from Google Calendar show up in Slack on time, and Slack can book, move and answer them
See scenarios →Rows of a Google Sheet become Google Calendar events with guests invited, and every move or cancellation in the calendar is written back to the sheet
See scenarios →Zadarma calls move Bitrix24 deals forward: a missed call becomes a task, a finished call updates the stage by your rules, and Bitrix24 automations can place a call themselves
See scenarios →A won deal in Bitrix24 becomes a sales document in 1С/BAS, and stock, payments and shipments from 1С/BAS come back to the deal
See scenarios →Implementation · Development · Integrations →
Bitrix24 ↔ Google Calendar — the system names are trademarks of their owners. CoreviaFlow is not affiliated with them unless stated otherwise.