Real-time
Two-way sync
Changes in Citus or Salesmate instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ CRM
Citus to Salesmate integration — real-time, two-way sync
Keep Citus and Salesmate 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 Salesmate
Treat Salesmate 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 Companies, Deals, Activities, Pipelines and Stages from Salesmate into Reference tables, Local tables, Schemas, Views in Citus with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Salesmate 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 Salesmate contacts and deals into a Postgres database or warehouse so SMB teams can report outside the CRM.
- 02 Keep contact segments aligned bi-directionally with an email marketing platform.
- 03 Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
- 04 Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
Common sync patterns
Trigger workflows from CRM changes
Field and stage updates in Salesmate arrive as row changes in Citus, ready to drive jobs and notifications.
Query the CRM like a database
Accounts, contacts, and custom objects from Salesmate 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 Salesmate, giving go-to-market teams live product context.
What you can sync between Citus and Salesmate
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 | Salesmate objects | How this pairing syncs | |
|---|---|---|---|
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Products Catalog items attached to deals, typically sourced from an ERP or billing system. | Reference tables is specific to Citus and Products to Salesmate — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Notes Free-text records synced for context in support or success tools. | Local tables is specific to Citus and Notes to Salesmate — 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. | Users Team member records used for ownership mapping. | Schemas is specific to Citus and Users to Salesmate — each maps to any object or custom field on the other side. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Contacts Person records synced with marketing tools and enrichment databases. | Views is specific to Citus and Contacts to Salesmate — 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. | Companies Organization records linked to contacts and deals. | Sequences is specific to Citus and Companies to Salesmate — 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. | Deals Pipeline opportunities with stage and value, synced out for revenue reporting. | Distributed tables is specific to Citus and Deals to Salesmate — each maps to any object or custom field on the other side. |
How changes propagate between Citus and Salesmate
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.
Citus Salesmate Sub-second propagation
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.
DeliveryEach detected change is written to Salesmate through its API, with automatic retries and rate-limit backoff.
Salesmate Citus Sub-second propagation
DetectionSalesmate notifies Stacksync of record changes through webhook events. Webhook triggers via the platform's automation features, with scheduled polling on modified timestamps as fallback.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Salesmate: Subject to the platform's API rate limits.
What ships with Citus ⇄ Salesmate
Connect Citus and Salesmate for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Salesmate connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Salesmate 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 Salesmate record.
Observability
Monitoring
Track your Citus ⇄ Salesmate 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 Salesmate.
How the Citus and Salesmate 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
Salesmate
- Integration surface
- REST API
- Authentication
- Access token (API key) sent as a request header
- Change detection
- Webhook triggers via the platform's automation features, with scheduled polling on modified timestamps as fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
How it works
How to connect Citus to Salesmate — 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 Citus and Salesmate with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Citus
connected
Salesmate
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and Salesmate 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 · Citus ⇄ SalesmateCustomers 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.
Citus SalesmateCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Salesmate integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Salesmate: authenticate both systems, choose the objects to sync (such as Citus's Reference tables and Local tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Salesmate: Webhook triggers via the platform's automation features, with scheduled polling on modified timestamps as fallback. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Salesmate side: Companies, Deals, Activities, Pipelines and Stages, plus custom fields where Salesmate exposes them. On the Citus side: Reference tables, Local tables, Schemas, Views. 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 Citus and Salesmate: Trigger workflows from CRM changes; Query the CRM like a database; Product events onto CRM records. Field and stage updates in Salesmate arrive as row changes in Citus, ready to drive jobs and notifications.
-
Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). Salesmate: REST API. Authentication: Access token (API key) sent as a request header. Stacksync manages authentication, retries, and rate limits on both sides.
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 190 integrations available for Citus and Salesmate.
Popular · 2 of 190
No integrations match .
