Skip to content
Business productivity ⇄ Human resources

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

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

Keep the people, teams, and status that eClinicalWorks and Smartrecruiters share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.

Each tool in eClinicalWorks keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Smartrecruiters is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.

Stacksync syncs Medications, Allergies, Immunizations, Documents in eClinicalWorks with Approvals, Candidates, Applications, Jobs in Smartrecruiters bi-directionally and in real time. A person added, moved, or offboarded in Smartrecruiters creates or updates the matching user in eClinicalWorks within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where eClinicalWorks captures details of its own, such as a corrected contact or a login identity, those can flow back to Smartrecruiters in whichever direction you configure.

Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.

Common use cases

  • 01 Feed appointment events to reminder and messaging platforms to reduce no-shows.
  • 02 Keep provider directories consistent between eClinicalWorks and scheduling or marketing systems.
  • 03 Export Interviews and Offers to a data warehouse to analyze interviewer load, offer-acceptance rates, and hiring outcomes.
  • 04 Subscribe to the Webhooks API to react to new applications and status changes in near real time across downstream systems.

Common sync patterns

Where eClinicalWorks routes or assigns work by person: assignments follow the org

When someone changes teams or managers in Smartrecruiters, the queues, ownership, or approvals in eClinicalWorks update to match, so work reaches whoever holds the role now.

Onboarding: access ready on day one

A new hire recorded in Smartrecruiters creates the matching user in eClinicalWorks with the right team and manager already set, so people can start working without waiting on a provisioning ticket.

Offboarding: no standing access after a departure

When someone is marked as leaving in Smartrecruiters, the matching account in eClinicalWorks is deactivated or flagged, so departures do not leave open access behind.

What you can sync between eClinicalWorks and Smartrecruiters

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 Smartrecruiters objects How this pairing syncs
Diagnostic reports Structured result reports grouping observations for a study or panel. Job Postings Job ads and publications pushed to the career site and job boards; created and managed via the job publication endpoints (rate-limited to 2 requests/sec). Diagnostic reports is specific to eClinicalWorks and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side.
Patients Demographic records exposed via FHIR Patient resources and HL7 ADT feeds; the anchor for all clinical syncs. Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. Patients is specific to eClinicalWorks and Interviews to Smartrecruiters — each maps to any object or custom field on the other side.
Appointments Scheduling records available via FHIR and HL7 SIU messages, synced for reminders and outreach. Offers Offer records tied to an Application with status, custom offer fields, and offer documents; readable and writable, commonly synced to an HRIS on hire (documents endpoint limited to 2 requests/sec). Appointments is specific to eClinicalWorks and Offers to Smartrecruiters — each maps to any object or custom field on the other side.
Encounters Visit records tying diagnoses, providers, and billing context together. Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. Encounters is specific to eClinicalWorks and Users to Smartrecruiters — each maps to any object or custom field on the other side.
Practitioners Provider records used to keep directories and scheduling systems consistent. Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. Practitioners is specific to eClinicalWorks and Approvals to Smartrecruiters — 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. Candidates Person records with contact details, tags, attachments, custom properties, and consent; created, updated, and searched via the Candidates API, often populated from sourcing or enrichment pipelines. Observations is specific to eClinicalWorks and Candidates to Smartrecruiters — each maps to any object or custom field on the other side.

How changes propagate between eClinicalWorks and Smartrecruiters

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 Smartrecruiters 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 Smartrecruiters through its API, with automatic retries and rate-limit backoff.

Smartrecruiters eClinicalWorks Sub-second propagation

DetectionSmartrecruiters notifies Stacksync of record changes through webhook events. Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs.

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.
  • Smartrecruiters: Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
What ships with eClinicalWorks ⇄ Smartrecruiters

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Smartrecruiters

Integration surface
SmartRecruiters REST APIs (SmartAPIs) on api.smartrecruiters.com — Candidates, Application, Jobs, Interviews, Offers, Users, Approvals, plus a Webhooks API for event subscriptions
Authentication
X-SmartToken API key header for a customer's own integration (grants full company access, no scopes or expiry), or OAuth 2.0 authorization-code flow for partner and Marketplace apps with user-scoped permissions
Change detection
Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs; otherwise poll list endpoints with updated-after-style filters. No log-based change data capture.
Capabilities
read · write · webhooks
Rate limits
Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
Smartrecruiters setup guide
How it works

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

    Choose tables

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

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

Popular · 8 of 439
All eClinicalWorks integrations All Smartrecruiters 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