Skip to content
Business productivity ⇄ CRM

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

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

Sync what happens in eClinicalWorks with the customer records in Intercom, in real time and in both directions.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever eClinicalWorks holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Stacksync connects Practitioners, Observations, Medications, Allergies in eClinicalWorks to Companies, Conversations, Tickets, Data Events in Intercom with bi-directional, real-time sync. Activity and record changes in eClinicalWorks update the matching contact or account in Intercom, and CRM data flows the other way wherever eClinicalWorks can store and use it.

Common use cases

  • Land encounter and billing-context data in a warehouse for utilization and revenue-cycle reporting.
  • Feed appointment events to reminder and messaging platforms to reduce no-shows.
  • Keep custom data attributes updated from billing or ERP systems so message segments reflect current plan and spend
  • Route qualified leads from Intercom conversations into the CRM as leads or opportunities in near real time

Where eClinicalWorks runs outreach

Prospects, sends, and replies sync into Intercom, keeping lead status current without manual imports.

Where eClinicalWorks supplies contact or company data

Enriched fields land directly on records in Intercom, and refreshes keep them from going stale.

Where eClinicalWorks processes payments

Charges, refunds, and subscription changes appear on the account in Intercom, so revenue context lives with the relationship.

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

eClinicalWorks objects Intercom objects
Patients Demographic records exposed via FHIR Patient resources and HL7 ADT feeds; the anchor for all clinical syncs. Contacts A single contact model covers both users and leads, distinguished by a role attribute.
Appointments Scheduling records available via FHIR and HL7 SIU messages, synced for reminders and outreach. Companies Company records group contacts and carry plan and account attributes used in segmentation.
Encounters Visit records tying diagnoses, providers, and billing context together. Conversations Support and sales threads sync outward for analytics and CRM context.
Practitioners Provider records used to keep directories and scheduling systems consistent. Tickets Structured ticket records track issues alongside conversational threads.
Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages. Data Events Behavioral events pushed in from product databases trigger messages and flows.
Medications Prescription and medication-list data within the patient record. Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data.
What ships with eClinicalWorks ⇄ Intercom

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the eClinicalWorks and Intercom connectors work

eClinicalWorks

Integration surface
FHIR R4 REST API plus HL7 v2 interfaces (ADT, SIU, ORU) through an interface engine
Authentication
OAuth 2.0 / SMART on FHIR for the FHIR API; site-configured credentials for HL7 interface connections
Change detection
HL7 interface feeds push event messages as they occur; the FHIR API is polled
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits and interface throughput agreements

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

    Choose tables

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

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

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for eClinicalWorks and Intercom.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.