Connect Google Calendar to OLT Sales CRM

Each OLT user authorizes their own Google account. Connection consent requests calendar.events, calendar.readonly, and userinfo.email. calendar.events authorizes meeting event changes, calendar.readonly authorizes primary-calendar event and availability reads, and userinfo.email identifies the connected address. Only scheduled CRM meetings assigned to a linked user with Calendar connected push to that user's primary calendar, while date-time events created or changed in Google synchronize into CRM on the five-minute poll.

• Assigned CRM meetings and invitations Only scheduled CRM meeting activities with a start time and an assigned representative linked to an OLT user with Calendar connected are created or updated on that user's primary calendar. Unless invitations are turned off for that meeting, Google sends updates to its attendees.
• Five-minute Calendar-to-CRM sync Date-time events created or changed on the connected user's primary Google Calendar synchronize into CRM meetings on the five-minute poll.
• Attendee and cancellation updates Linked meeting edits and cancellations are reconciled, and Google attendee response changes are reflected on the CRM meeting's attendee records.
• Google Meet creation Choosing Google Meet for a new CRM meeting asks Google to create the conference link and stores the returned link on the CRM activity.
• Calendar-aware conflict checks Scheduling checks CRM meetings together with busy intervals from the selected host's primary calendar without exposing external event subjects, attendees, or notes.
• Public one-to-one booking links An active Sales CRM seller can publish a shareable one-to-one booking link only with their own Google Calendar connected. The personalized URL stays noindex and nofollow and exposes only open times after OLT applies working hours, the chosen duration, before-and-after buffers, minimum notice, CRM meetings, and busy intervals from the seller's primary calendar. If OLT cannot verify current Calendar availability, it stops availability and booking. A successful booking sends the guest a Google invitation, records the CRM meeting, and either reuses the matching CRM contact or creates a lead contact.
• An OLT member with Sales CRM access The meeting host needs a linked member account so OLT can use that person's calendar rather than another member's calendar.
• The member's own Google account Each member completes Google's consent flow from Settings → Integrations. Connection consent requests calendar.events, calendar.readonly, and userinfo.email. calendar.events authorizes meeting event changes, calendar.readonly authorizes primary-calendar event and availability reads, and userinfo.email identifies the connected address. Gmail and Calendar can be connected or disconnected independently, so either connection can remain active without the other.
• An available Google OAuth connection The OLT deployment must have Google OAuth configured, and connection access can depend on enabled modules, plan, role, Google access policy, and provider configuration.
• Each member connects separately One member's connection does not authorize a colleague's calendar, and OLT does not fall back to another person's connected account.
• Primary calendar only OLT reads and writes the connected member's primary calendar; secondary, shared, and resource calendars are not synchronized.
• Timed events only Only events with a date and time are synchronized into CRM meetings. All-day events are skipped.
• First connection starts with future events The initial calendar import begins at the current time rather than importing the member's past calendar history.
• Calendar imports do not infer CRM context A newly imported Google Calendar event can create a CRM meeting and associate recognized attendee records, but OLT does not infer the meeting's opportunity, company, or primary-contact context. An authorized CRM editor must attach that context.
• Expired-cursor recovery is bounded If Google's incremental-sync cursor expires, OLT recovers from the last successful poll with overlap bounded to no more than 30 days and stores a replacement cursor only after every page succeeds.
• Provider failures remain retryable If Google rejects a CRM-to-Calendar create, the CRM meeting remains saved and the result is marked as a provider failure so the synchronization can be retried.
• Disconnecting does not remove existing events Disconnecting stops two-way synchronization, but meetings already present on Google Calendar remain there.
• CRM meetings can still be saved If the assigned host has no Google Calendar connected, OLT keeps the CRM meeting without creating a Google event, Meet link, or calendar invitations.