Skip to content
Database ⇄ CRM

Citus to Intercom integration — real-time, two-way sync

Keep Citus and Intercom 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 Intercom

Treat Intercom 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, Conversations, Tickets, Data Events from Intercom into Schemas, Views, Sequences, Distributed tables in Citus with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Intercom 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 contacts and companies bi-directionally with the CRM so support sees deal context and sales sees conversation history
  • 02 Push product usage events from an application database into Intercom to trigger onboarding and retention messages
  • 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 Intercom arrive as row changes in Citus, ready to drive jobs and notifications.

Query the CRM like a database

Accounts, contacts, and custom objects from Intercom 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 Intercom, giving go-to-market teams live product context.

What you can sync between Citus and Intercom

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 Intercom objects How this pairing syncs
Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Tickets Structured ticket records track issues alongside conversational threads. Schemas is specific to Citus and Tickets to Intercom — 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. Data Events Behavioral events pushed in from product databases trigger messages and flows. Views is specific to Citus and Data Events to Intercom — 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. Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. Sequences is specific to Citus and Custom Data Attributes to Intercom — 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. Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. Distributed tables is specific to Citus and Tags to Intercom — 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. Segments Saved audience definitions are readable for targeting parity across tools. Reference tables is specific to Citus and Segments to Intercom — each maps to any object or custom field on the other side.
Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Admins & Teams Teammate records map conversation ownership to CRM users. Local tables is specific to Citus and Admins & Teams to Intercom — each maps to any object or custom field on the other side.

How changes propagate between Citus and Intercom

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 Intercom 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 Intercom through its API, with automatic retries and rate-limit backoff.

Intercom Citus Sub-second propagation

DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.

DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Intercom: Subject to per-app rate limits on the Intercom API.
What ships with Citus ⇄ Intercom

Connect Citus and Intercom for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Intercom connection.

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Citus or Intercom 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 Intercom record.

Observability

Monitoring

Track your Citus ⇄ Intercom 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 Intercom.

How the Citus and Intercom 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

Intercom

Integration surface
REST API
Authentication
OAuth 2.0 for public apps or a workspace access token
Change detection
Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to per-app rate limits on the Intercom API
How it works

How to connect Citus to Intercom — 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 Intercom 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
    Intercom connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Citus and Intercom 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 ⇄ Intercom
    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 Intercom
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Citus and Intercom integration FAQ

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.

Learn more about security
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:

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 439 integrations available for Citus and Intercom.

Popular · 6 of 439
All Citus integrations All Intercom 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