Real-time
Two-way sync
Changes in Nutshell or Zoom instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Communications
Nutshell to Zoom integration — real-time, two-way sync
Keep Nutshell and Zoom 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 Nutshell and Zoom
Keep Nutshell and Zoom 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. Zoom 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 Tasks, Notes, Products, Tags in Nutshell with Meetings, Webinars, Registrants, Cloud Recordings in Zoom field by field, in real time, and in both directions. Current contact details flow out to Zoom so it can reach the right person, and the calls, messages, and meetings Zoom 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 Push Zoom Phone call logs into an operational database so sales and support calls are logged against the right customer records.
- 04 Keep Team Chat channel membership aligned with team and department data mastered in an operational database.
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 Nutshell appears in Zoom within seconds, so outreach starts without exporting a list or re-keying numbers.
Where Zoom reaches out: contacts kept current
Names, phone numbers, email addresses, and the owning rep from Nutshell stay current in Zoom, so every call, text, or email goes to the right person at the right address.
What you can sync between Nutshell and Zoom
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.
| Nutshell objects | Zoom objects | How this pairing syncs | |
|---|---|---|---|
| Users Rep records used to resolve ownership when syncing assignments | Users Account members with license type, role, and status; created, updated, and deactivated two-way to sync with HRIS or identity systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Products Line items attached to leads, used to sync sold products into billing | Team Chat Channels and Messages Chat channels, membership, and messages; listed and sent two-way to align collaboration spaces with team data. | Products is specific to Nutshell and Team Chat Channels and Messages to Zoom — each maps to any object or custom field on the other side. | |
| Tags Segmentation labels mapped to lists or filters in downstream tools | Groups User groups that carry policy and settings; membership synced from department or team data in an operational database. | Tags is specific to Nutshell and Groups to Zoom — each maps to any object or custom field on the other side. | |
| Leads Nutshell's deal object; synced as the pipeline record linked to people and companies | Meetings Scheduled and instant meetings with join URLs and settings; created and updated from a CRM or calendar, read back for reporting. | Leads is specific to Nutshell and Meetings to Zoom — each maps to any object or custom field on the other side. | |
| People Individual contacts, kept consistent with marketing and outreach tools | Webinars Webinar events (requires the Webinar license); created and managed via API, with panelists and settings written from event tools. | People is specific to Nutshell and Webinars to Zoom — each maps to any object or custom field on the other side. | |
| Companies Account records that group people and leads for account-level syncs | Registrants Meeting and webinar registrant records; added, listed, and status-updated so signups flow between event platforms and Zoom. | Companies is specific to Nutshell and Registrants to Zoom — each maps to any object or custom field on the other side. |
How changes propagate between Nutshell and Zoom
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.
Nutshell Zoom 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 Zoom through its API, with automatic retries and rate-limit backoff.
Zoom Nutshell Sub-second propagation
DetectionZoom notifies Stacksync of record changes through webhook events. Webhooks via Event Subscriptions (meeting.started/ended, participant joined/left, user.created/updated, recording.completed, and more) for real-time.
DeliveryEach detected change is written to Nutshell through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Nutshell: Subject to the platform's API rate limits.
- Zoom: APIs are grouped into Light, Medium, Heavy, and Resource-intensive categories with per-second and daily quotas that scale by plan (e.g. Business+ Heavy APIs allow 40/second within a 60,000/day combined cap); exceeding a limit returns HTTP 429.
What ships with Nutshell ⇄ Zoom
Connect Nutshell and Zoom for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Nutshell–Zoom connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Nutshell or Zoom 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 Nutshell or Zoom record.
Observability
Monitoring
Track your Nutshell ⇄ Zoom sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Nutshell and Zoom.
How the Nutshell and Zoom connectors work
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
Zoom
- Integration surface
- REST API (v2) with webhook Event Subscriptions
- Authentication
- OAuth 2.0 — user-authorized OAuth or Server-to-Server OAuth using account credentials; access tokens are valid for one hour and requests use granular per-resource scopes (e.g. meeting:read, user:write)
- Change detection
- Webhooks via Event Subscriptions (meeting.started/ended, participant joined/left, user.created/updated, recording.completed, and more) for real-time events, with polling on list endpoints using date-range filters for backfill and objects without an event
- Capabilities
- read · write · webhooks
- Rate limits
- APIs are grouped into Light, Medium, Heavy, and Resource-intensive categories with per-second and daily quotas that scale by plan (e.g. Business+ Heavy APIs allow 40/second within a 60,000/day combined cap); exceeding a limit returns HTTP 429.
How it works
How to connect Nutshell to Zoom — 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 Nutshell and Zoom with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Nutshell
connected
Zoom
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Nutshell and Zoom 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 · Nutshell ⇄ ZoomCustomers 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.
Nutshell ZoomCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Nutshell and Zoom integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Nutshell and Zoom: authenticate both systems, choose the objects to sync (such as Nutshell's Users and Products), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Nutshell and Zoom connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Nutshell–Zoom integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Nutshell and Zoom. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Nutshell: Webhook subscriptions for record events, with polling as fallback. On Zoom: Webhooks via Event Subscriptions (meeting.started/ended, participant joined/left, user.created/updated, recording.completed, and more) for real-time events, with polling on list endpoints using date-range filters for backfill and objects without an event. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Nutshell side: Tasks, Notes, Products, Tags, plus custom fields where Nutshell exposes them. On the Zoom side: Meetings, Webinars, Registrants, Cloud Recordings. 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.
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 324 integrations available for Nutshell and Zoom.
Popular · 8 of 324
-
Nutshell ⇄ Gmail -
Nutshell ⇄ Amazon SES -
Nutshell ⇄ Infobip -
Nutshell ⇄ Aircall -
Zoom ⇄ Gorgias -
Zoom ⇄ Infor CRM -
Zoom ⇄ Insightly -
Zoom ⇄ Intercom
No integrations match .
