Skip to content
Data warehouse ⇄ CRM

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

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

Sync Intercom into Exasol continuously and push warehouse results back onto CRM records, one two-way connection instead of two pipelines.

The CRM feeds the warehouse and the warehouse should feed the CRM: relationship data flows one way, and computed scores, segments, and customer context flow back. Most teams build the first half as a batch pipeline and never quite get to the second.

Stacksync does both with one connection. Companies, Conversations, Tickets, Data Events from Intercom land in Exasol as live tables, updated within seconds, and columns computed in Exasol write back to fields in Intercom. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.

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 Keep dimension tables such as customers and products aligned with the systems of record.
  • 04 Load CRM and ERP records into Exasol tables on a schedule so analysts query fresh operational data.

Common sync patterns

Scores and segments back on the record

Lead scores, churn risk, or usage segments computed in Exasol appear as fields in Intercom, where the people working accounts actually see them.

A single customer view

Join Intercom's relationship data with billing, product, and support data in Exasol to build the customer picture the CRM alone cannot hold.

Cleanup that sticks

Deduplication and normalization done in Exasol can be written back, so warehouse-side cleanup actually fixes the CRM.

What you can sync between Exasol 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.

Exasol objects Intercom objects How this pairing syncs
Views Read-only query surfaces often used as curated sources for reverse ETL. Contacts A single contact model covers both users and leads, distinguished by a role attribute. Views is specific to Exasol and Contacts to Intercom — each maps to any object or custom field on the other side.
Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. Companies Company records group contacts and carry plan and account attributes used in segmentation. Virtual schemas is specific to Exasol and Companies to Intercom — each maps to any object or custom field on the other side.
UDF scripts In-database functions that can transform synced data after load. Conversations Support and sales threads sync outward for analytics and CRM context. UDF scripts is specific to Exasol and Conversations to Intercom — each maps to any object or custom field on the other side.
Users and roles Grant read/write access for the dedicated integration account. Tickets Structured ticket records track issues alongside conversational threads. Users and roles is specific to Exasol and Tickets to Intercom — each maps to any object or custom field on the other side.
Schemas Namespaces that group the tables a sync reads from or writes into. Data Events Behavioral events pushed in from product databases trigger messages and flows. Schemas is specific to Exasol and Data Events to Intercom — each maps to any object or custom field on the other side.
Tables Primary sync target; columnar relational tables written with standard SQL. Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. Tables is specific to Exasol and Custom Data Attributes to Intercom — each maps to any object or custom field on the other side.

How changes propagate between Exasol 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.

Exasol Intercom Interval-based propagation

DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.

DeliveryEach detected change is written to Intercom through its API, with automatic retries and rate-limit backoff.

Intercom Exasol 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 Exasol as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
  • Intercom: Subject to per-app rate limits on the Intercom API.
What ships with Exasol ⇄ Intercom

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Exasol ⇄ Intercom sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Exasol and Intercom.

How the Exasol and Intercom connectors work

Exasol

Integration surface
SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
Authentication
Database credentials (username and password)
Change detection
Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
Capabilities
read · write
Rate limits
No API quota; concurrency is bounded by cluster resources and session limits

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 Exasol 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 Exasol 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
    Exasol connected
    Intercom connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Exasol 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 Exasol and Intercom.

Popular · 6 of 439
All Exasol 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