Two-way sync
Changes in BambooHR or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Keep BambooHR and InterSystems IRIS in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
BambooHR 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: Time Off, Employment Status, Departments and Divisions, Custom Tables in BambooHR need to exist as queryable Globals, Namespaces, Stored Procedures, Tables 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 Globals, Namespaces, Stored Procedures, Tables in InterSystems IRIS with Time Off, Employment Status, Departments and Divisions, Custom Tables in BambooHR field by field, in real time. You decide which system owns which fields — BambooHR 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.
Groups, departments, managers, and reporting lines from BambooHR stay consistent in InterSystems IRIS, so hierarchy-driven logic and permissions don't drift.
Values assembled or corrected in InterSystems IRIS write onto the matching record in BambooHR where those fields are writable, keeping the people system enriched.
Records maintained in BambooHR land as queryable Globals, Namespaces, Stored Procedures, Tables in InterSystems IRIS, so internal apps and dashboards read live data instead of a periodic export.
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.
| BambooHR objects | InterSystems IRIS objects | How this pairing syncs | |
|---|---|---|---|
| Compensation Effective-dated pay rate, schedule, and change reason; read into planning and payroll systems with access restricted to authorized fields. | Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Compensation is specific to BambooHR and Stored Procedures to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Time Off Requests, balances, and policies; read for absence calendars and capacity planning, with approved requests written from an external scheduling tool. | Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Time Off is specific to BambooHR and Tables to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Employment Status Effective-dated hire, leave, and termination status; drives automated provisioning and deprovisioning in downstream identity and license systems. | Views SQL views expose curated slices of data for outbound replication. | Employment Status is specific to BambooHR and Views to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Departments and Divisions Org-structure list values; synced to keep cost centers and team groupings consistent across ERP, identity, and analytics systems. | Schemas Schema organization scopes which tables a sync connection can see. | Departments and Divisions is specific to BambooHR and Schemas to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Custom Tables Company-specific effective-dated tables (assets, training, certifications); rows read and written so custom HR data isn't trapped in the HRIS. | Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Custom Tables is specific to BambooHR and Persistent Classes to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Reports Saved company reports retrievable via API; read out on a schedule to feed a warehouse without rebuilding field-by-field queries. | Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Reports is specific to BambooHR and Globals to InterSystems IRIS — 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.
DetectionBambooHR notifies Stacksync of record changes through webhook events. The Get Updated Employee IDs endpoint (last-changed timestamps) returns employees inserted, updated, or deleted since a cursor for efficient polling.
DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.
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 BambooHR through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BambooHR–InterSystems IRIS connection.
Changes in BambooHR or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever BambooHR or InterSystems IRIS data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single BambooHR or InterSystems IRIS record.
Track your BambooHR ⇄ InterSystems IRIS sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between BambooHR and InterSystems IRIS.
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 BambooHR and InterSystems IRIS 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 BambooHR and InterSystems IRIS 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 BambooHR and InterSystems IRIS: authenticate both systems, choose the objects to sync (such as BambooHR's Compensation and Time Off), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the InterSystems IRIS side: Globals, Namespaces, Stored Procedures, Tables, plus custom fields where InterSystems IRIS exposes them. On the BambooHR side: Time Off, Employment Status, Departments and Divisions, Custom Tables. Stacksync auto-detects both schemas and converts types between the two systems.
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 BambooHR and InterSystems IRIS: Org and structure stay aligned; Computed and operational fields flow back; Mirror people records into the database. Groups, departments, managers, and reporting lines from BambooHR stay consistent in InterSystems IRIS, so hierarchy-driven logic and permissions don't drift.
BambooHR: BambooHR API (REST, per-company subdomain). Authentication: API key per user over HTTP Basic auth (key as username), scoped to that user's permission level in BambooHR; OAuth/OpenID available for SSO-enabled apps. InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. Stacksync manages authentication, retries, and rate limits on both sides.
InterSystems IRIS: IRIS is multi-model: the same stored data can be accessed as relational tables via SQL, as persistent objects, and as multidimensional globals, so integrations usually standardize on the SQL projection. BambooHR: Webhooks are configured per monitored field set and post changed employee data to your endpoint; they complement rather than replace the updated-IDs polling cursor. Stacksync's field mapping accounts for these differences between BambooHR and InterSystems IRIS without custom code.
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 375 integrations available for BambooHR and InterSystems IRIS.