Skip to content
CommsOperator
Capability record updated 2026-09-27

Connect the systems you use. See the limits before the call.

Gmail connects directly to Google. Microsoft 365 connects through Microsoft Graph. Every other entry below says whether it is native, assisted, an import path, or not supported.

CommsOperator connects directly to Gmail through Google OAuth and the Gmail API, and to Microsoft 365 through Microsoft Graph. Gmail is authorized one named mailbox at a time; Microsoft also supports shared mailboxes and an organization-wide connector approved by IT. The catalogue labels each available path as native, assisted, import-only, or unsupported. The legacy Unipile module remains inactive and is not used for Gmail.

Request accessCompare alternatives
Email

Direct Gmail and Microsoft 365 connections

Both providers feed the shared inbox, but their authorization and currently verified send scope are different.

Email

Native connection

Gmail and Google Workspace (production beta)

Direct Google OAuth and Gmail API connection for a named mailbox. No aggregator sits between CommsOperator and Google.

  • Connect one Gmail or Google Workspace mailbox with explicit Google consent
  • Read the authorized mailbox profile and message listing directly through the Gmail API
  • Keep messages already imported when Google pauses an initial sync at its quota boundary

Current limit: Production beta: full initial-sync recovery remains under live verification after a Google quota pause. Compose, reply, and forward are implemented, but no production Gmail send has been verified. Gmail is mailbox by mailbox, with no Google organization-wide admin connector and no Gmail campaign sequences today.

Email

Native connection

Microsoft 365 and Outlook

Microsoft Graph connection for a person's mailbox, a shared mailbox, or an organization-wide tenant connector approved by IT.

  • Individual OAuth and organization-wide admin consent
  • Inbox and sent-mail sync, shared mailboxes, attachments, compose and reply
  • Approval-gated campaigns and sequences from authorized mailboxes
  • Outlook calendar booking and Microsoft Teams meeting transcripts

Current limit: The organization connector is Microsoft-only. A mailbox must be enabled both for sending and for reply ingestion before campaign use.

The rest of the stack

Native where the path is sanctioned. Explicit where it is not.

A legacy selector or dormant module is not an integration claim. These are the paths tenants can actually plan around.

Collaboration

Native connection

Microsoft Teams

Project-channel updates, action buttons, linked threads, meeting transcripts, and CRM timeline context.

  • Channel notifications
  • Bot actions
  • Linked discussion threads
  • Meeting transcript ingestion

Current limit: A verified project-to-channel mapping and authorized Microsoft identity are required.

Customer experience

Native connection

Website widgets and forms

Chat, help search, feedback, roadmap, changelog, booking, and verified lead capture on your own sites.

  • Unified launcher
  • Public and private feedback
  • Help center search
  • Signed public lead ingestion

Current limit: You install and configure the script or form endpoint on each site.

Social

Assisted bridge

LinkedIn Pages

Page messages can enter the inbox through an operator-run browser bridge, with a person sending every reply.

  • Assisted message capture
  • Human-reviewed replies

Current limit: This is not an unattended official-API automation and should not be chosen for high-volume social support.

CRM and data

Native connection

Apollo.io, Reoon, Decile Hub, Qoralytics

Optional enrichment, verification, fund-CRM, and attribution connections used by the relevant workspace.

  • On-demand enrichment
  • Email verification
  • Fund CRM context
  • Attribution events

Current limit: Each integration is optional and has its own credentials, scope, and provider contract.

CRM migration

Import or API

HubSpot and Salesforce

Migration sources through controlled CSV import or the public leads API, with email matching and suppression carried first.

  • Dry-run import
  • Email-based identity matching
  • Suppression-preserving migration

Current limit: These are not live bidirectional CRM syncs.

Messaging

Not supported

WhatsApp, Instagram, Facebook Messenger, X, Telegram, and SMS

Not supported. No message is sent or received on these channels.

Current limit: A few legacy channel types may still appear in settings, but the retired connector is inactive for tenants.

Integration questions buyers ask

Does Gmail use Unipile or another mailbox aggregator?

No. The active Gmail module connects directly to Google OAuth and the Gmail API. The older Unipile module is retained only as inactive legacy code and is not the Gmail path offered to tenants.

Can IT connect every Google Workspace mailbox at once?

Not today. Gmail is authorized one named mailbox at a time. Microsoft 365 has a separate organization-wide connector for administrators who want to approve multiple mailboxes centrally.

Will connecting CommsOperator move our mail?

No. Gmail stays in Google and Outlook mail stays in Microsoft 365. CommsOperator keeps the working copy needed for shared ownership, search, AI drafts, and the CRM timeline.

Tell us the mailbox and systems you need.

We will confirm the exact connection path, limits, region, and onboarding work before you commit.

Request accessRead the trust center