Real-time
Two-way sync
Changes in Hibob or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Database
Hibob to InterSystems IRIS integration — real-time, two-way sync
Keep Hibob 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.
- 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 Hibob and InterSystems IRIS
Put your workforce data where your apps can reach it: InterSystems IRIS and Hibob share the same people, positions, and org structure in real time.
Hibob 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: Documents, Named lists, People (Employees), Employment in Hibob need to exist as queryable Tables, Views, Schemas, Persistent Classes 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 Tables, Views, Schemas, Persistent Classes in InterSystems IRIS with Documents, Named lists, People (Employees), Employment in Hibob field by field, in real time. You decide which system owns which fields — Hibob 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.
Common use cases
- 01 Replicate IRIS tables to Postgres so application teams can build against a familiar database
- 02 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access
- 03 Push Salaries and Variable Pay from Bob into a payroll provider or warehouse each pay cycle, using the Payroll-permitted service user.
- 04 Mirror Work data (department, site, manager, title) into an org-chart or reporting warehouse for headcount and structure analysis.
Common sync patterns
Computed and operational fields flow back
Values assembled or corrected in InterSystems IRIS write onto the matching record in Hibob where those fields are writable, keeping the people system enriched.
Mirror people records into the database
Records maintained in Hibob land as queryable Tables, Views, Schemas, Persistent Classes in InterSystems IRIS, so internal apps and dashboards read live data instead of a periodic export.
One directory of record
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
What you can sync between Hibob and InterSystems IRIS
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.
| Hibob objects | InterSystems IRIS objects | How this pairing syncs | |
|---|---|---|---|
| Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. | Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Salaries is specific to Hibob and Globals to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. | Namespaces Namespaces partition databases and determine the connection context for integrations. | Time off is specific to Hibob and Namespaces to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. | Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Lifecycle is specific to Hibob and Stored Procedures to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. | Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Documents is specific to Hibob and Tables to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. | Views SQL views expose curated slices of data for outbound replication. | Named lists is specific to Hibob and Views to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| People (Employees) Core employee records with out-of-the-box and custom fields; read via POST /people/search, created and updated through the /people endpoints. | Schemas Schema organization scopes which tables a sync connection can see. | People (Employees) is specific to Hibob and Schemas to InterSystems IRIS — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and InterSystems IRIS
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.
Hibob InterSystems IRIS Sub-second propagation
DetectionHibob notifies Stacksync of record changes through webhook events. Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events.
DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.
InterSystems IRIS Hibob Interval-based propagation
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 Hibob through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Hibob: Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
- InterSystems IRIS: Constrained by database resources rather than published API rate limits.
What ships with Hibob ⇄ InterSystems IRIS
Connect Hibob and InterSystems IRIS for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–InterSystems IRIS connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or InterSystems IRIS 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 Hibob or InterSystems IRIS record.
Observability
Monitoring
Track your Hibob ⇄ InterSystems IRIS sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Hibob and InterSystems IRIS.
How the Hibob and InterSystems IRIS connectors work
Hibob
- Integration surface
- REST API (the Bob API)
- Authentication
- Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin
- Change detection
- Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event).
- Capabilities
- read · write · webhooks
- Rate limits
- Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
InterSystems IRIS
- Integration surface
- SQL over JDBC/ODBC, plus object and REST access layers
- Authentication
- Database credentials
- Change detection
- Polling (timestamp or query-based); no standard webhook surface
- Capabilities
- read · write
- Rate limits
- Constrained by database resources rather than published API rate limits
How it works
How to connect Hibob to InterSystems IRIS — 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.
- 01
Connect your apps
Authenticate Hibob 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.
Hibob
connected
InterSystems IRIS
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob 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.
objects · Hibob ⇄ InterSystems IRISCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Hibob InterSystems IRISCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and InterSystems IRIS integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and InterSystems IRIS: authenticate both systems, choose the objects to sync (such as Hibob's Salaries and Time off), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Hibob and InterSystems IRIS. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Hibob: Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event). On InterSystems IRIS: Polling (timestamp or query-based); no standard webhook surface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the InterSystems IRIS side: Tables, Views, Schemas, Persistent Classes, plus custom fields where InterSystems IRIS exposes them. On the Hibob side: Documents, Named lists, People (Employees), Employment. 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 Hibob and InterSystems IRIS: Computed and operational fields flow back; Mirror people records into the database; One directory of record. Values assembled or corrected in InterSystems IRIS write onto the matching record in Hibob where those fields are writable, keeping the people system enriched.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 467 integrations available for Hibob and InterSystems IRIS.
Popular · 7 of 467
-
Hibob ⇄ PostgreSQL -
Hibob ⇄ Amazon RDS -
Hibob ⇄ Supabase -
Hibob ⇄ MySQL -
InterSystems IRIS ⇄ Jobvite -
InterSystems IRIS ⇄ Lever -
InterSystems IRIS ⇄ Paylocity
No integrations match .
