Connect Google Workspace to OLT Sales CRM

Each OLT member connects their own Google account and authorizes Gmail and Google Calendar separately. Gmail sends through that member's address and, when gmail.readonly is granted, synchronizes new Inbox and Sent activity after connection. Calendar supports CRM meetings and availability checks against that member's primary calendar.

  • Per-user connection Every participating member completes Google's consent flow from Settings → Integrations. One member's connection never substitutes for a colleague's mailbox or calendar.
  • Independent Gmail and Calendar controls Gmail and Google Calendar have separate connection states. A member can authorize either workflow or both, and disconnecting one does not disconnect the other.
  • Buyer value with explicit boundaries Sales teams can send from their own address, file permitted new mailbox activity in CRM, schedule supported meetings, and check primary-calendar availability without claiming older email or calendar history.

Per-user setup and required Google grants

The OLT deployment needs Google OAuth configured, and each participating member must approve the grants for the workflows they choose.

  • Active member and Google account The signed-in person needs an active OLT membership, access to Settings → Integrations, and access to the Google account they want to connect.
  • Gmail grants gmail.send authorizes sending through the member's Gmail address. gmail.readonly separately authorizes post-connection Inbox and Sent synchronization, and userinfo.email identifies the connected address.
  • Google Calendar grants calendar.events authorizes meeting event changes. calendar.readonly authorizes primary-calendar event and availability reads, and userinfo.email identifies the connected address.
  • Google Workspace policy A Google Workspace administrator may need to allow OLT when the organization's Google access policy requires app approval.

Gmail sending and post-connection inbox synchronization

OLT uses the connected member's Gmail grants independently for sending and mailbox synchronization.

  • Send through the member's Gmail address Supported customer email written in OLT can send through that member's connected Gmail address and appears in the Gmail Sent folder.
  • Synchronize new mailbox activity after connection When gmail.readonly was granted, OLT checks new Inbox and Sent changes on the five-minute poll and reconciles supported messages into CRM email activities.
  • Inbound attachment retention is best-effort up to 25 MB OLT attempts to retain inbound Gmail attachments of 25 MB or less. Oversized files, or attachment download, storage, or persistence failures, leave the CRM email activity intact without guaranteeing that file is available.
  • No Gmail history import before connection The first successful inbox synchronization saves Gmail's current mailbox cursor. Messages already in the mailbox are not imported as historical CRM activity.
  • Expired Gmail cursor recovery is limited If Gmail's incremental cursor expires, OLT starts recovery from the last successful poll with a 5-minute overlap, but looks back no more than 30 days and reads at most 20 provider pages before storing a replacement cursor. Messages older than the 30-day window or beyond the 20-page cap may leave a gap in CRM activity.
  • Read access is separate from sending gmail.send can support sending without gmail.readonly. In that state, mailbox messages remain in Gmail and are not synchronized into CRM activities.
  • Personal sending does not choose the company sender Connecting a personal Gmail account does not change the organization's default sender for automatic company email; an owner or administrator controls that separate choice.
  • Uncertain Gmail delivery stops automatic fallback When Google's response leaves delivery uncertain, OLT stops automatic fallback and records the send as failed, so the same message cannot reach the recipient twice. Only a confirmed Gmail rejection or a confirmed non-attempt may retry through the organization's configured sender on a verified domain; without that verified sender, the send stays failed.

Google Calendar meetings and availability

Supported CRM meetings and primary-calendar busy intervals use the assigned member's own active Google Calendar connection.

  • Create and reconcile CRM meetings Scheduled CRM meetings assigned to a connected member can create or update events on that member's primary calendar with attendee invitations, and supported edits, responses, and cancellations are reconciled.
  • Create Google Meet links When Google Meet is selected for a new CRM meeting, OLT asks Google to create the conference link and stores the link Google returns.
  • Check primary-calendar availability Scheduling checks combine CRM meetings 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.
  • Primary calendar only OLT reads and writes only the connected member's primary calendar. Secondary, shared, and resource calendars are not synchronized.
  • Timed events only Only Google events with a date-time start are reconciled into CRM meetings. Date-only all-day events are skipped.
  • Future-only initial Calendar import The first inbound Calendar synchronization starts at the current time rather than importing earlier 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.