Skip to content
Business productivity ⇄ CRM

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

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

Sync what happens in eClinicalWorks with the customer records in Salesforce, 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 Diagnostic reports, Patients, Appointments, Encounters in eClinicalWorks to Cases, Campaigns, Tasks and Events, Products and Price Books in Salesforce with bi-directional, real-time sync. Activity and record changes in eClinicalWorks update the matching contact or account in Salesforce, and CRM data flows the other way wherever eClinicalWorks can store and use it.

Common use cases

  • Push referral or intake data captured in external forms into the EHR via HL7 interfaces.
  • Sync patient demographics and appointments into a CRM so patient outreach and intake teams work from current data.
  • Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
  • Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.

Where eClinicalWorks supplies contact or company data

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

Where eClinicalWorks processes payments

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

Where eClinicalWorks can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Salesforce sync into eClinicalWorks, so people working there have the context without switching tools.

What you can sync between eClinicalWorks and Salesforce

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 Salesforce objects
Patients Demographic records exposed via FHIR Patient resources and HL7 ADT feeds; the anchor for all clinical syncs. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce.
Appointments Scheduling records available via FHIR and HL7 SIU messages, synced for reminders and outreach. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated.
Encounters Visit records tying diagnoses, providers, and billing context together. Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP.
Practitioners Provider records used to keep directories and scheduling systems consistent. Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records.
Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages. Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines.
Medications Prescription and medication-list data within the patient record. Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close.
What ships with eClinicalWorks ⇄ Salesforce

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your eClinicalWorks ⇄ Salesforce 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 Salesforce.

How the eClinicalWorks and Salesforce 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

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide
How it works

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

    Choose tables

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

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

Popular · 8 of 386
All eClinicalWorks integrations All Salesforce 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