Skip to content
Database ⇄ CRM

Citus to Nutshell integration — real-time, two-way sync

Keep Citus 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 Citus and Nutshell

Treat Nutshell like part of your database: its records live in Citus 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 Citus, where it can be queried and joined like everything else.

Stacksync mirrors Tags, Users, Leads, People from Nutshell into Schemas, Views, Sequences, Distributed tables in Citus 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

  • Mirror tasks and activities into ops tools for cross-team visibility.
  • Sync Nutshell leads into a warehouse or Postgres so small B2B teams can report on pipeline without exports.
  • Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
  • Consolidate per-tenant rows from distributed tables into per-customer reporting databases.

Query the CRM like a database

Accounts, contacts, and custom objects from Nutshell become tables in Citus you can join with application data directly.

Product events onto CRM records

Signup, usage, or lifecycle changes written to Citus 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.

What you can sync between Citus 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.

Citus objects Nutshell objects
Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Tags Segmentation labels mapped to lists or filters in downstream tools
Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Users Rep records used to resolve ownership when syncing assignments
Views Curated projections over distributed data, often used as read-only sync sources. Leads Nutshell's deal object; synced as the pipeline record linked to people and companies
Sequences Key generators that matter when external writes must not collide with application inserts. People Individual contacts, kept consistent with marketing and outreach tools
Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Companies Account records that group people and leads for account-level syncs
Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. Activities Logged calls, meetings, and emails used for engagement reporting
What ships with Citus ⇄ Nutshell

Connect Citus and Nutshell for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Citus or Nutshell instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Citus 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 Citus or Nutshell record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Citus and Nutshell.

How the Citus and Nutshell connectors work

Citus

Integration surface
PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
Authentication
Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
Change detection
PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
Capabilities
read · write · CDC

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 Citus 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.

  1. 01

    Connect your apps

    Authenticate Citus 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Citus connected
    Nutshell connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Citus 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Citus ⇄ Nutshell
    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
    Citus Nutshell
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Citus and Nutshell integration FAQ

SECURITY

Security teams love 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.

Learn more about security
SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Citus and Nutshell.

Popular · 8 of 386
All Citus integrations All Nutshell integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own