Skip to content
Business productivity ⇄ Accounting and finance

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

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

Connect the financial records in Recurly with the work happening in eClinicalWorks, so both stay current without exports or copy-paste.

Recurly holds the financial truth: who the customers are, what they were billed, what they paid. eClinicalWorks is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.

Stacksync keeps Accounts, Subscriptions, Plans, Invoices in Recurly and Allergies, Immunizations, Documents, Diagnostic reports in eClinicalWorks in sync, bi-directionally and in real time. Whatever records eClinicalWorks keeps and whatever events it produces, the overlap with Recurly is mapped field by field, and a change on either side shows up on the other within seconds.

There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.

Common use cases

  • 01 Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.
  • 02 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
  • 03 Feed appointment events to reminder and messaging platforms to reduce no-shows.
  • 04 Keep provider directories consistent between eClinicalWorks and scheduling or marketing systems.

Common sync patterns

Where eClinicalWorks collects payments or triggers charges: events land in Recurly

Payment and charge activity flows into Recurly as it happens, so the books reflect reality without manual reconciliation.

Where eClinicalWorks tracks people or companies: one identity

A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.

Where eClinicalWorks handles customer conversations: billing context in view

Front-line teams see invoice and payment status from Recurly next to the customer they are helping, without logging into the finance system.

What you can sync between eClinicalWorks and Recurly

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 Recurly objects How this pairing syncs
Appointments Scheduling records available via FHIR and HL7 SIU messages, synced for reminders and outreach. Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Appointments is specific to eClinicalWorks and Transactions to Recurly — each maps to any object or custom field on the other side.
Encounters Visit records tying diagnoses, providers, and billing context together. Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Encounters is specific to eClinicalWorks and Line Items to Recurly — each maps to any object or custom field on the other side.
Practitioners Provider records used to keep directories and scheduling systems consistent. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Practitioners is specific to eClinicalWorks and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side.
Observations Labs and vitals, delivered via FHIR resources or HL7 ORU result messages. Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). Observations is specific to eClinicalWorks and Billing Info to Recurly — each maps to any object or custom field on the other side.
Medications Prescription and medication-list data within the patient record. Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Medications is specific to eClinicalWorks and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side.
Allergies Allergy and intolerance entries in the clinical record. Accounts Customer/billing entity records keyed by account_code; the anchor most subscriptions and invoices hang off. Synced two-way with CRM accounts or a customer database. Allergies is specific to eClinicalWorks and Accounts to Recurly — each maps to any object or custom field on the other side.

How changes propagate between eClinicalWorks and Recurly

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.

eClinicalWorks Recurly Interval-based propagation

DetectionStacksync polls eClinicalWorks for changes on an incremental schedule, reading only records changed since the previous pass. HL7 interface feeds push event messages as they occur.

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

Recurly eClinicalWorks Sub-second propagation

DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.

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

Rate-limit considerations

  • eClinicalWorks: Subject to the platform's API rate limits and interface throughput agreements.
  • Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
What ships with eClinicalWorks ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Recurly

Integration surface
REST API (V3, date-versioned; legacy V2 XML API also exists)
Authentication
API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
Change detection
Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
Capabilities
read · write · webhooks
Rate limits
Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
How it works

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

    Choose tables

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

eClinicalWorks and Recurly 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
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 434 integrations available for eClinicalWorks and Recurly.

Popular · 7 of 434
All eClinicalWorks integrations All Recurly 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