Real-time
Two-way sync
Changes in DuckDB or Seismic instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ CRM
DuckDB to Seismic integration — real-time, two-way sync
Keep DuckDB and Seismic 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 DuckDB and Seismic
Treat Seismic like part of your database: its records live in DuckDB 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 DuckDB, where it can be queried and joined like everything else.
Stacksync mirrors Teamsites, LiveSend Links, Digital Sales Rooms, Reporting Activities from Seismic into Views, External files (Parquet/CSV/JSON), Attached databases, Database files in DuckDB with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Seismic 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 Sync Library Content metadata and Custom Property Schemas with a DAM or PIM so one taxonomy governs assets across systems.
- 02 React to ContentManager and DSR webhook events to update a database when documents are published, versioned, or expired.
- 03 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
- 04 Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.
Common sync patterns
Internal tools without API code
Back-office apps read and write the synced tables; Stacksync handles the Seismic API, limits, and retries.
Trigger workflows from CRM changes
Field and stage updates in Seismic arrive as row changes in DuckDB, ready to drive jobs and notifications.
Query the CRM like a database
Accounts, contacts, and custom objects from Seismic become tables in DuckDB you can join with application data directly.
What you can sync between DuckDB and Seismic
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.
| DuckDB objects | Seismic objects | How this pairing syncs | |
|---|---|---|---|
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Digital Sales Rooms Buyer-facing microsites (DSRs); lifecycle and content-change events surface via webhooks, currently marked Early Access. | Attached databases is specific to DuckDB and Digital Sales Rooms to Seismic — each maps to any object or custom field on the other side. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Reporting Activities Content-interaction, engagement, and usage analytics extracted read-only through the ETL-oriented Reporting API v2 for a warehouse. | Database files is specific to DuckDB and Reporting Activities to Seismic — each maps to any object or custom field on the other side. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Library Content Documents, decks, and assets stored in teamsites; created, moved, and retrieved via the Content Management API, each with a contentId. | Schemas is specific to DuckDB and Library Content to Seismic — each maps to any object or custom field on the other side. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Content Versions Version history for a library item; new versions upload via API and old ones expire, with events firing on ContentManager webhooks. | Tables is specific to DuckDB and Content Versions to Seismic — each maps to any object or custom field on the other side. | |
| Views SQL views used to shape or filter data for downstream consumers. | Users User records managed through SCIM 2.0 and legacy user endpoints; created, updated, and deactivated for provisioning sync. | Views is specific to DuckDB and Users to Seismic — each maps to any object or custom field on the other side. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | User Groups Group definitions and membership that govern content access; synced from an IdP or HRIS to keep permissions current. | External files (Parquet/CSV/JSON) is specific to DuckDB and User Groups to Seismic — each maps to any object or custom field on the other side. |
How changes propagate between DuckDB and Seismic
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.
DuckDB Seismic Interval-based propagation
DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.
DeliveryEach detected change is written to Seismic through its API, with automatic retries and rate-limit backoff.
Seismic DuckDB Sub-second propagation
DetectionSeismic notifies Stacksync of record changes through webhook events. Webhooks for content, version, user, group, workflow, DSR, and LiveSend events.
DeliveryEach detected change is applied to DuckDB as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
- Seismic: Tiered per-endpoint limits over a rolling 60-second window; exceeding returns HTTP 429, with X-Seismic-Remaining-Calls and X-Seismic-Total-Calls headers.
What ships with DuckDB ⇄ Seismic
Connect DuckDB and Seismic for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Seismic connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever DuckDB or Seismic 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 DuckDB or Seismic record.
Observability
Monitoring
Track your DuckDB ⇄ Seismic sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between DuckDB and Seismic.
How the DuckDB and Seismic connectors work
DuckDB
- Integration surface
- In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
- Authentication
- None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
- Change detection
- Polling or full re-reads; no change feed or transaction log API
- Capabilities
- read · write
- Rate limits
- No API rate limits; throughput is bounded by local compute and I/O
Seismic
- Integration surface
- REST Integration APIs and Reporting API v2
- Authentication
- OAuth 2.0 / OpenID Connect; Bearer token in the Authorization header, via Authorization Code (user context) or client-credentials app-only flows
- Change detection
- Webhooks for content, version, user, group, workflow, DSR, and LiveSend events; the Reporting API v2 is polled for batch historical extracts (ETL-oriented, not high-frequency)
- Capabilities
- read · write · webhooks
- Rate limits
- Tiered per-endpoint limits over a rolling 60-second window; exceeding returns HTTP 429, with X-Seismic-Remaining-Calls and X-Seismic-Total-Calls headers
How it works
How to connect DuckDB to Seismic — 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 DuckDB and Seismic with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
DuckDB
connected
Seismic
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the DuckDB and Seismic 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 · DuckDB ⇄ SeismicCustomers 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.
DuckDB SeismicCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
DuckDB and Seismic integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between DuckDB and Seismic: authenticate both systems, choose the objects to sync (such as DuckDB's Attached databases and Database files), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both DuckDB and Seismic. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on DuckDB: Polling or full re-reads; no change feed or transaction log API. On Seismic: Webhooks for content, version, user, group, workflow, DSR, and LiveSend events; the Reporting API v2 is polled for batch historical extracts (ETL-oriented, not high-frequency). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Seismic side: Teamsites, LiveSend Links, Digital Sales Rooms, Reporting Activities, plus custom fields where Seismic exposes them. On the DuckDB side: Views, External files (Parquet/CSV/JSON), Attached databases, Database files. 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 DuckDB and Seismic: Internal tools without API code; Trigger workflows from CRM changes; Query the CRM like a database. Back-office apps read and write the synced tables; Stacksync handles the Seismic API, limits, and retries.
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
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 471 integrations available for DuckDB and Seismic.
Popular · 4 of 471
No integrations match .
