Real-time
Two-way sync
Changes in Nutshell or PostgreSQL instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Database
Nutshell to PostgreSQL integration — real-time, two-way sync
Keep Nutshell and PostgreSQL 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 PostgreSQL
Treat Nutshell like part of your database: its records live in PostgreSQL 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 PostgreSQL, where it can be queried and joined like everything else.
Stacksync mirrors Companies, Activities, Tasks, Notes from Nutshell into Schemas, Columns, Primary and Unique Keys, JSONB Columns in PostgreSQL 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
- Push closed-won leads to accounting software to trigger invoicing automatically.
- Keep People and Companies consistent between Nutshell and email marketing or outreach tools.
- Let an application write to its own database and have those rows appear as records in business systems in near real time
- Consolidate data from several microservice databases into one operational Postgres store
Trigger workflows from CRM changes
Field and stage updates in Nutshell arrive as row changes in PostgreSQL, ready to drive jobs and notifications.
Query the CRM like a database
Accounts, contacts, and custom objects from Nutshell become tables in PostgreSQL you can join with application data directly.
Product events onto CRM records
Signup, usage, or lifecycle changes written to PostgreSQL sync onto the matching records in Nutshell, giving go-to-market teams live product context.
What you can sync between Nutshell and PostgreSQL
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 | PostgreSQL objects | |
|---|---|---|
| Tags Segmentation labels mapped to lists or filters in downstream tools | Schemas Namespaces that scope which tables a sync reads and writes. | |
| Users Rep records used to resolve ownership when syncing assignments | Columns Field-level mapping targets; types are mapped to the connected system's field types. | |
| Leads Nutshell's deal object; synced as the pipeline record linked to people and companies | Primary and Unique Keys Used as match keys for idempotent upserts and conflict resolution. | |
| People Individual contacts, kept consistent with marketing and outreach tools | JSONB Columns Hold semi-structured payloads such as nested SaaS objects or metadata. | |
| Companies Account records that group people and leads for account-level syncs | Sequences Generate surrogate keys for rows created by inbound syncs. | |
| Activities Logged calls, meetings, and emails used for engagement reporting | Custom Types and Enums Constrain synced values to a fixed set, mirroring picklist fields. |
What ships with Nutshell ⇄ PostgreSQL
Connect Nutshell and PostgreSQL for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Nutshell–PostgreSQL connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Nutshell or PostgreSQL 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 PostgreSQL record.
Observability
Monitoring
Track your Nutshell ⇄ PostgreSQL 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 PostgreSQL.
How the Nutshell and PostgreSQL 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
PostgreSQL
- Integration surface
- SQL wire protocol (PostgreSQL frontend/backend protocol)
- Authentication
- Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host); a least-privilege DB user
- Change detection
- Logical replication (wal_level = logical) for change data capture via the "Postgres" connector; database triggers (TRIGGER grant + stacksync_logging schema) via the trigger-based "Postgres Heroku" connector where
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by connection limits, instance resources, and replication slot throughput
How it works
How to connect Nutshell to PostgreSQL — 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 PostgreSQL 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
PostgreSQL
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Nutshell and PostgreSQL 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 ⇄ PostgreSQLCustomers 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 PostgreSQLCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Nutshell and PostgreSQL integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Nutshell and PostgreSQL: authenticate both systems, choose the objects to sync (such as Nutshell's Tags and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Nutshell: The deal object is called a Lead in Nutshell, and it links to separate People and Company records rather than replacing them. PostgreSQL: Logical decoding of the write-ahead log (wal_level=logical) provides row-level change capture without adding triggers to user tables. Stacksync's field mapping accounts for these differences between Nutshell and PostgreSQL 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 PostgreSQL records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Nutshell and PostgreSQL connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Nutshell–PostgreSQL integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Nutshell and PostgreSQL. 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 PostgreSQL: Logical replication (wal_level = logical) for change data capture via the "Postgres" connector; database triggers (TRIGGER grant + stacksync_logging schema) via the trigger-based "Postgres Heroku" connector where. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Nutshell and PostgreSQL.
Popular · 8 of 386
-
Nutshell ⇄ MongoDB -
Nutshell ⇄ CockroachDB -
Nutshell ⇄ Google AlloyDB -
Nutshell ⇄ Dynamo DB -
PostgreSQL ⇄ HubSpot -
PostgreSQL ⇄ Microsoft Dynamics 365 Sales -
PostgreSQL ⇄ Attio -
PostgreSQL ⇄ Pipedrive
No integrations match .
