Skip to content
Communications ⇄ CRM

Gmail to Intercom integration — real-time, two-way sync

Keep Gmail and Intercom in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Gmail and Intercom

Keep Intercom and Gmail working from the same contacts, and log every call, message, and meeting back on the record, in real time and in both directions.

Intercom holds the people the business talks to: the contacts, their phone numbers and email addresses, and which rep owns the relationship. Gmail is where the talking happens, whether that is calls, texts, email, or meetings. The two depend on the same people, and when the contact list in one drifts from the other, outreach goes to stale numbers and the record of what was said never makes it back to the account.

Stacksync syncs Companies, Conversations, Tickets, Data Events in Intercom with Threads, Labels, Drafts, Attachments in Gmail field by field, in real time, and in both directions. Current contact details flow out to Gmail so it can reach the right person, and the calls, messages, and meetings Gmail produces flow back onto the matching record in Intercom. You decide which system owns which fields, and conflicts resolve by rules you set.

Common use cases

  • 01 Sync contacts and companies bi-directionally with the CRM so support sees deal context and sales sees conversation history
  • 02 Push product usage events from an application database into Intercom to trigger onboarding and retention messages
  • 03 Mirror Labels with pipeline or ticket states so triage done in an external tool is reflected inside the inbox.
  • 04 Log sent and received Messages onto CRM contact and deal timelines automatically so reps never copy-paste email history.

Common sync patterns

One contact list, opt-outs included

A number, address, or unsubscribe recorded in either system updates the other, so no one calls a disconnected line or messages someone who opted out.

New contacts reachable right away

A contact created or updated in Intercom appears in Gmail within seconds, so outreach starts without exporting a list or re-keying numbers.

Where Gmail reaches out: contacts kept current

Names, phone numbers, email addresses, and the owning rep from Intercom stay current in Gmail, so every call, text, or email goes to the right person at the right address.

What you can sync between Gmail and Intercom

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Gmail objects Intercom objects How this pairing syncs
Attachments File payloads referenced by message part; read out to storage or a document system for archival and compliance workflows. Tickets Structured ticket records track issues alongside conversational threads. Attachments is specific to Gmail and Tickets to Intercom — each maps to any object or custom field on the other side.
History The incremental change log keyed by historyId; used for efficient delta sync so only mailbox changes since the last cursor are fetched. Data Events Behavioral events pushed in from product databases trigger messages and flows. History is specific to Gmail and Data Events to Intercom — each maps to any object or custom field on the other side.
Messages Individual emails with headers, body, and label state; read out to a CRM or warehouse for activity logging, and sent or modified two-way from sales tools. Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. Messages is specific to Gmail and Custom Data Attributes to Intercom — each maps to any object or custom field on the other side.
Threads Conversation groupings that keep replies together; synced so a CRM timeline or support desk shows the full exchange, not isolated messages. Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. Threads is specific to Gmail and Tags to Intercom — each maps to any object or custom field on the other side.
Labels User and system labels (INBOX, SENT, custom); applied and removed via sync to mirror pipeline stages or triage states from an external system. Segments Saved audience definitions are readable for targeting parity across tools. Labels is specific to Gmail and Segments to Intercom — each maps to any object or custom field on the other side.
Drafts Unsent messages; created and updated from templates or sequence tools so reps review before sending from their own mailbox. Admins & Teams Teammate records map conversation ownership to CRM users. Drafts is specific to Gmail and Admins & Teams to Intercom — each maps to any object or custom field on the other side.

How changes propagate between Gmail and Intercom

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Gmail Intercom Sub-second propagation

DetectionGmail notifies Stacksync of record changes through webhook events. Incremental sync via users.history.list from a stored historyId cursor, plus real-time push notifications through Google Cloud Pub/Sub watch on the.

DeliveryEach detected change is written to Intercom through its API, with automatic retries and rate-limit backoff.

Intercom Gmail Sub-second propagation

DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.

DeliveryEach detected change is written to Gmail through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Gmail: Quota is measured in units per user per second (e.g. messages.list = 5 units, messages.send = 100 units) against a 250 quota-unit/user/second limit and a daily project cap; exceeding limits returns 429 with exponential backoff expected.
  • Intercom: Subject to per-app rate limits on the Intercom API.
What ships with Gmail ⇄ Intercom

Connect Gmail and Intercom for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Gmail–Intercom connection.

Real-time

Two-way sync

Changes in Gmail or Intercom instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Gmail or Intercom data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Gmail or Intercom record.

Observability

Monitoring

Track your Gmail ⇄ Intercom sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Gmail and Intercom.

How the Gmail and Intercom connectors work

Gmail

Integration surface
Gmail API (REST, v1)
Authentication
OAuth 2.0 via Google — user-authorized consent with granular scopes (gmail.readonly, gmail.modify, gmail.send, gmail.labels); restricted scopes require Google's app verification for production use
Change detection
Incremental sync via users.history.list from a stored historyId cursor, plus real-time push notifications through Google Cloud Pub/Sub watch on the mailbox (watch must be renewed at least every 7 days)
Capabilities
read · write · webhooks
Rate limits
Quota is measured in units per user per second (e.g. messages.list = 5 units, messages.send = 100 units) against a 250 quota-unit/user/second limit and a daily project cap; exceeding limits returns 429 with exponential backoff expected.

Intercom

Integration surface
REST API
Authentication
OAuth 2.0 for public apps or a workspace access token
Change detection
Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to per-app rate limits on the Intercom API
How it works

How to connect Gmail to Intercom — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Gmail and Intercom with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Gmail connected
    Intercom connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Gmail and Intercom objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Gmail ⇄ Intercom
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Gmail Intercom
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Gmail and Intercom integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 364 integrations available for Gmail and Intercom.

Popular · 7 of 364
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.