Real-time
Two-way sync
Changes in Nutshell or YugabyteDB instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Database
Nutshell to YugabyteDB integration — real-time, two-way sync
Keep Nutshell and YugabyteDB 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 YugabyteDB
Treat Nutshell like part of your database: its records live in YugabyteDB as real tables, and writes in either place sync to the other in seconds.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in YugabyteDB, where it can be queried and joined like everything else.
Stacksync mirrors Products, Tags, Users, Leads from Nutshell into CDC Streams, Databases and Keyspaces, Tables, Indexes in YugabyteDB with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Nutshell with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.
Common use cases
- 01 Mirror tasks and activities into ops tools for cross-team visibility.
- 02 Sync Nutshell leads into a warehouse or Postgres so small B2B teams can report on pipeline without exports.
- 03 Run log-based CDC from YugabyteDB tables into a warehouse for analytics without batch dumps.
- 04 Two-way sync between YugabyteDB application tables and a CRM so product data and account records stay consistent.
Common sync patterns
Product events onto CRM records
Signup, usage, or lifecycle changes written to YugabyteDB sync onto the matching records in Nutshell, giving go-to-market teams live product context.
Internal tools without API code
Back-office apps read and write the synced tables; Stacksync handles the Nutshell API, limits, and retries.
Trigger workflows from CRM changes
Field and stage updates in Nutshell arrive as row changes in YugabyteDB, ready to drive jobs and notifications.
What you can sync between Nutshell and YugabyteDB
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 | YugabyteDB objects | How this pairing syncs | |
|---|---|---|---|
| Notes Free-text history attached to leads and contacts, replicated for a full timeline | Schemas Postgres-style namespaces in YSQL used to organize synced data. | Notes is specific to Nutshell and Schemas to YugabyteDB — each maps to any object or custom field on the other side. | |
| Products Line items attached to leads, used to sync sold products into billing | Sequences ID generation objects relevant when syncing writes into YSQL tables. | Products is specific to Nutshell and Sequences to YugabyteDB — each maps to any object or custom field on the other side. | |
| Tags Segmentation labels mapped to lists or filters in downstream tools | CDC Streams Change streams over the storage-layer WAL consumed through logical replication or Debezium-compatible connectors. | Tags is specific to Nutshell and CDC Streams to YugabyteDB — each maps to any object or custom field on the other side. | |
| Users Rep records used to resolve ownership when syncing assignments | Databases and Keyspaces Top-level containers for the YSQL (Postgres-style) and YCQL (Cassandra-style) APIs respectively. | Users is specific to Nutshell and Databases and Keyspaces to YugabyteDB — 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 | Tables Distributed SQL tables split into tablets; the primary read and write targets. | Leads is specific to Nutshell and Tables to YugabyteDB — each maps to any object or custom field on the other side. | |
| People Individual contacts, kept consistent with marketing and outreach tools | Indexes Global secondary indexes maintained transactionally alongside table writes. | People is specific to Nutshell and Indexes to YugabyteDB — each maps to any object or custom field on the other side. |
How changes propagate between Nutshell and YugabyteDB
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 YugabyteDB 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 applied to YugabyteDB as a row-level write, with types converted between the two schemas.
YugabyteDB Nutshell Sub-second propagation
DetectionChanges in YugabyteDB are captured at the source via change data capture — no polling loop against its API. Native CDC from the write-ahead log via PostgreSQL logical replication or Debezium-compatible connectors.
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.
- YugabyteDB: No API rate limits; throughput scales with cluster nodes and tablet distribution.
What ships with Nutshell ⇄ YugabyteDB
Connect Nutshell and YugabyteDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Nutshell–YugabyteDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Nutshell or YugabyteDB 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 YugabyteDB record.
Observability
Monitoring
Track your Nutshell ⇄ YugabyteDB 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 YugabyteDB.
How the Nutshell and YugabyteDB 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
YugabyteDB
- Integration surface
- SQL wire protocol (PostgreSQL-compatible YSQL) plus a Cassandra-compatible YCQL API
- Authentication
- Database credentials
- Change detection
- Native CDC from the write-ahead log via PostgreSQL logical replication or Debezium-compatible connectors
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput scales with cluster nodes and tablet distribution.
How it works
How to connect Nutshell to YugabyteDB — 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 YugabyteDB 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
YugabyteDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Nutshell and YugabyteDB 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 ⇄ YugabyteDBCustomers 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 YugabyteDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Nutshell and YugabyteDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Nutshell and YugabyteDB: authenticate both systems, choose the objects to sync (such as Nutshell's Notes and Products), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Nutshell and YugabyteDB: Product events onto CRM records; Internal tools without API code; Trigger workflows from CRM changes. Signup, usage, or lifecycle changes written to YugabyteDB sync onto the matching records in Nutshell, giving go-to-market teams live product context.
-
Nutshell: JSON-RPC API over HTTPS; a newer REST API is also offered. Authentication: HTTP Basic with account email and API key. YugabyteDB: SQL wire protocol (PostgreSQL-compatible YSQL) plus a Cassandra-compatible YCQL API. Authentication: Database credentials. Stacksync manages authentication, retries, and rate limits on both sides.
-
Nutshell: Authentication uses HTTP Basic with an account email and API key, so no OAuth flow is required for server-to-server sync. YugabyteDB: CDC is exposed from the storage-layer WAL through PostgreSQL logical replication and Debezium-compatible connectors. Stacksync's field mapping accounts for these differences between Nutshell and YugabyteDB without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Nutshell and YugabyteDB records are not retained after a sync operation.
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 345 integrations available for Nutshell and YugabyteDB.
Popular · 3 of 345
No integrations match .
