Skip to content
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

  • Sync Salesmate contacts and deals into a Postgres database or warehouse so SMB teams can report outside the CRM.
  • Keep contact segments aligned bi-directionally with an email marketing platform.
  • 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.

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
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.
Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Notes Free-text records synced for context in support or success tools.
Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Users Team member records used for ownership mapping.
Views Curated projections over distributed data, often used as read-only sync sources. Contacts Person records synced with marketing tools and enrichment databases.
Sequences Key generators that matter when external writes must not collide with application inserts. Companies Organization records linked to contacts and deals.
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.
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.

Real-time

Two-way sync

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

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.

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

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Citus connected
    Salesmate connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 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.

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

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

Popular · 8 of 386
All Citus integrations All Salesmate 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