Real-time
Two-way sync
Changes in Gmail or Nutshell instantly reflect in both systems. No stale data, no manual imports.
Communications ⇄ CRM
Gmail to Nutshell integration — real-time, two-way sync
Keep Gmail and Nutshell 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 Nutshell
Keep Nutshell 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.
Nutshell 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 Leads, People, Companies, Activities in Nutshell with Drafts, Attachments, History, Messages 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 Nutshell. You decide which system owns which fields, and conflicts resolve by rules you set.
Common use cases
- 01 Keep People and Companies consistent between Nutshell and email marketing or outreach tools.
- 02 Write subscription or product data from internal systems into Nutshell so reps see account context.
- 03 Read Attachments and message metadata into a warehouse or document store for retention, discovery, and compliance reporting.
- 04 Mirror Labels with pipeline or ticket states so triage done in an external tool is reflected inside the inbox.
Common sync patterns
New contacts reachable right away
A contact created or updated in Nutshell 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 Nutshell stay current in Gmail, so every call, text, or email goes to the right person at the right address.
Calls, messages, and meetings on the record
Activity handled in Gmail appears on the matching contact and account in Nutshell, so the next person sees the full history without leaving the CRM.
What you can sync between Gmail and Nutshell
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 | Nutshell objects | How this pairing syncs | |
|---|---|---|---|
| History The incremental change log keyed by historyId; used for efficient delta sync so only mailbox changes since the last cursor are fetched. | Companies Account records that group people and leads for account-level syncs | History is specific to Gmail and Companies to Nutshell — 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. | Activities Logged calls, meetings, and emails used for engagement reporting | Messages is specific to Gmail and Activities to Nutshell — 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. | Tasks Rep to-dos mirrored into external work-management or reporting systems | Threads is specific to Gmail and Tasks to Nutshell — 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. | Notes Free-text history attached to leads and contacts, replicated for a full timeline | Labels is specific to Gmail and Notes to Nutshell — 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. | Products Line items attached to leads, used to sync sold products into billing | Drafts is specific to Gmail and Products to Nutshell — each maps to any object or custom field on the other side. | |
| Attachments File payloads referenced by message part; read out to storage or a document system for archival and compliance workflows. | Tags Segmentation labels mapped to lists or filters in downstream tools | Attachments is specific to Gmail and Tags to Nutshell — each maps to any object or custom field on the other side. |
How changes propagate between Gmail and Nutshell
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 Nutshell 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 Nutshell through its API, with automatic retries and rate-limit backoff.
Nutshell Gmail Sub-second propagation
DetectionNutshell notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling as fallback.
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.
- Nutshell: Subject to the platform's API rate limits.
What ships with Gmail ⇄ Nutshell
Connect Gmail and Nutshell for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Gmail–Nutshell connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Gmail or Nutshell 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 Nutshell record.
Observability
Monitoring
Track your Gmail ⇄ Nutshell 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 Nutshell.
How the Gmail and Nutshell 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.
Nutshell
- Integration surface
- JSON-RPC API over HTTPS; a newer REST API is also offered
- Authentication
- HTTP Basic with account email and API key
- Change detection
- webhook subscriptions for record events, with polling as fallback
- Capabilities
- read · write · webhooks
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Gmail to Nutshell — 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.
- 01
Connect your apps
Authenticate Gmail and Nutshell with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Gmail
connected
Nutshell
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Gmail and Nutshell 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.
objects · Gmail ⇄ NutshellCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Gmail NutshellCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Gmail and Nutshell integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Gmail and Nutshell: authenticate both systems, choose the objects to sync (such as Gmail's History and Messages), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Gmail and Nutshell. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Gmail: 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). On Nutshell: Webhook subscriptions for record events, with polling as fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Nutshell side: Leads, People, Companies, Activities, plus custom fields where Nutshell exposes them. On the Gmail side: Drafts, Attachments, History, Messages. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Gmail and Nutshell: New contacts reachable right away; Where Gmail reaches out: contacts kept current; Calls, messages, and meetings on the record. A contact created or updated in Nutshell appears in Gmail within seconds, so outreach starts without exporting a list or re-keying numbers.
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 271 integrations available for Gmail and Nutshell.
Popular · 8 of 271
-
Gmail ⇄ Chorusai -
Gmail ⇄ Clari -
Gmail ⇄ Dun And Bradstreet -
Gmail ⇄ Seismic -
Nutshell ⇄ RingCentral -
Nutshell ⇄ Zoom -
Nutshell ⇄ Amazon SES -
Nutshell ⇄ Infobip
No integrations match .
