Two-way sync
Changes in InterSystems IRIS or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep InterSystems IRIS 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.
Smartrecruiters is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. InterSystems IRIS is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Approvals, Candidates, Applications, Jobs in Smartrecruiters need to exist as queryable Persistent Classes, Globals, Namespaces, Stored Procedures in InterSystems IRIS before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.
Stacksync syncs Persistent Classes, Globals, Namespaces, Stored Procedures in InterSystems IRIS with Approvals, Candidates, Applications, Jobs in Smartrecruiters field by field, in real time. You decide which system owns which fields — Smartrecruiters typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.
The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
Approvals, Candidates, Applications, Jobs replicate into InterSystems IRIS where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
Groups, departments, managers, and reporting lines from Smartrecruiters stay consistent in InterSystems IRIS, so hierarchy-driven logic and permissions don't drift.
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.
| InterSystems IRIS objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Tables is specific to InterSystems IRIS and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Views SQL views expose curated slices of data for outbound replication. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Views is specific to InterSystems IRIS and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Schemas Schema organization scopes which tables a sync connection can see. | 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. | Schemas is specific to InterSystems IRIS and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Applications Links a Candidate to a Job and carries the current hiring status and source; created and advanced through statuses (screening, interview, offer, hired, rejected) via the Application API. | Persistent Classes is specific to InterSystems IRIS and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Jobs Requisitions (positions) with openings, departments, locations, and hiring team; created, patched, and read out for requisition and time-to-fill reporting via the Jobs API. | Globals is specific to InterSystems IRIS and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Namespaces Namespaces partition databases and determine the connection context for integrations. | 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). | Namespaces is specific to InterSystems IRIS and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. |
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.
DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
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 applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–Smartrecruiters connection.
Changes in InterSystems IRIS or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever InterSystems IRIS or Smartrecruiters data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single InterSystems IRIS or Smartrecruiters record.
Track your InterSystems IRIS ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and Smartrecruiters.
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 InterSystems IRIS 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.
Pick the InterSystems IRIS 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.
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 InterSystems IRIS and Smartrecruiters: authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Tables and Views), 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 InterSystems IRIS and Smartrecruiters: One directory of record; Reporting and analytics on current data; Org and structure stay aligned. When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. Smartrecruiters: 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. Stacksync manages authentication, retries, and rate limits on both sides.
InterSystems IRIS: InterSystems positions IRIS as the successor to Caché, and it is widely deployed under healthcare and financial applications. Smartrecruiters: SmartRecruiters exposes a genuine two-way API — Candidates, Applications, Jobs, Job Postings, Interviews, and Offers can be created and updated, and applications moved through hiring statuses, not just read. Stacksync's field mapping accounts for these differences between InterSystems IRIS and Smartrecruiters 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 InterSystems IRIS and Smartrecruiters 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 467 integrations available for InterSystems IRIS and Smartrecruiters.