Two-way sync
Changes in eClinicalWorks or Intercom instantly reflect in both systems. No stale data, no manual imports.
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.
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.
Prospects, sends, and replies sync into Intercom, keeping lead status current without manual imports.
Enriched fields land directly on records in Intercom, and refreshes keep them from going stale.
Charges, refunds, and subscription changes appear on the account in Intercom, so revenue context lives with the relationship.
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. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every eClinicalWorks–Intercom connection.
Changes in eClinicalWorks or Intercom instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever eClinicalWorks or Intercom data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single eClinicalWorks or Intercom record.
Track your eClinicalWorks ⇄ Intercom sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between eClinicalWorks and Intercom.
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.
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.
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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between eClinicalWorks and Intercom: authenticate both systems, choose the objects to sync (such as eClinicalWorks's Patients and Appointments), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 eClinicalWorks and Intercom: Where eClinicalWorks runs outreach; Where eClinicalWorks supplies contact or company data; Where eClinicalWorks processes payments. Prospects, sends, and replies sync into Intercom, keeping lead status current without manual imports.
eClinicalWorks: 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. Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. Stacksync manages authentication, retries, and rate limits on both sides.
eClinicalWorks: All patient data is PHI, so integrations must run under HIPAA business associate agreements with appropriate access controls. Intercom: Intercom's Contacts API unifies users and leads into one object with a role attribute, replacing the older separate users and leads endpoints. Stacksync's field mapping accounts for these differences between eClinicalWorks and Intercom without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means eClinicalWorks and Intercom records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for eClinicalWorks and Intercom.