Real-time sync
Changes in Citus or Dun And Bradstreet instantly reflect in both systems. No stale data, no manual imports.
Keep Citus and Dun And Bradstreet in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Dun And Bradstreet is a read-only source: Stacksync reads its data in real time and delivers it into Citus, so Citus always reflects the current state of Dun And Bradstreet — without exports, scripts, or schedulers.
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.
Signup, usage, or lifecycle changes written to Citus sync onto the matching records in Dun And Bradstreet, giving go-to-market teams live product context.
Back-office apps read and write the synced tables; Stacksync handles the Dun And Bradstreet API, limits, and retries.
Field and stage updates in Dun And Bradstreet arrive as row changes in Citus, ready to drive jobs and notifications.
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 | Dun And Bradstreet objects | How this pairing syncs | |
|---|---|---|---|
| Views Curated projections over distributed data, often used as read-only sync sources. | Principals & Contacts (Data Block) Company officers, executives, and contacts tied to a D-U-N-S Number; read-only enrichment used to populate CRM contact and account-owner fields. | Views is specific to Citus and Principals & Contacts (Data Block) to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. | Sequences is specific to Citus and Company Hierarchy & Connections (Family Tree) to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Financial Strength & Risk Insight (Data Block) D&B risk and credit signals - D&B Rating, PAYDEX, Failure Score, Delinquency Score, Viability - keyed by D-U-N-S Number; read-only. | Distributed tables is specific to Citus and Financial Strength & Risk Insight (Data Block) to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Identity Resolution (Match / cleanseMatch) Sends a company name and address and returns ranked candidate DUNS with confidence codes and a MatchGrade; read-only scored match, not an exact lookup. | Reference tables is specific to Citus and Identity Resolution (Match / cleanseMatch) to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Criteria Search Query companies by firmographic criteria (industry, geography, size) and get back a list of D-U-N-S Numbers to enrich; read-only list building. | Local tables is specific to Citus and Criteria Search to Dun And Bradstreet — each maps to any object or custom field on the other side. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Monitoring Notifications Change notices for a registered portfolio of DUNS; read-only feed pulled from the notifications endpoint (retained ~60 days) or delivered as bundled push. | Schemas is specific to Citus and Monitoring Notifications to Dun And Bradstreet — each maps to any object or custom field on the other side. |
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.
DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.
DeliveryDun And Bradstreet does not accept inbound record writes, so this direction carries requests rather than records: Dun And Bradstreet's output flows back as field updates on the originating Citus records.
DetectionStacksync polls Dun And Bradstreet for changes on an incremental schedule, reading only records changed since the previous pass. Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days).
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Dun And Bradstreet connection.
Changes in Citus or Dun And Bradstreet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Citus or Dun And Bradstreet data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Citus or Dun And Bradstreet record.
Track your Citus ⇄ Dun And Bradstreet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Citus and Dun And Bradstreet.
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.
Authenticate Citus and Dun And Bradstreet with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Citus and Dun And Bradstreet 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time integration between Citus and Dun And Bradstreet — Dun And Bradstreet is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and Dun And Bradstreet connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Dun And Bradstreet integration in-house.
Yes — Stacksync ships production-grade connectors for both Citus and Dun And Bradstreet. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. On Dun And Bradstreet: Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days). Bundled push delivery is configured with your D&B rep; there is no standard HTTP webhook and no log-based CDC. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Dun And Bradstreet side: Financial Strength & Risk Insight (Data Block), Identity Resolution (Match / cleanseMatch), Criteria Search, Monitoring Notifications, plus custom fields where Dun And Bradstreet exposes them. On the Citus side: Reference tables, Local tables, Schemas, Views. Stacksync auto-detects both schemas and converts types between the two systems.
Dun And Bradstreet is a read-only source, so this integration runs one-way: Stacksync reads from Dun And Bradstreet in real time and delivers into Citus. Field mapping and monitoring work the same as for two-way pairs.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 409 integrations available for Citus and Dun And Bradstreet.