Real-time
Two-way sync
Changes in DEAR Inventory or Hibob instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Human resources
DEAR Inventory to Hibob integration — real-time, two-way sync
Keep DEAR Inventory and Hibob 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 DEAR Inventory and Hibob
Sync the workers, org structure, and cost centers that DEAR Inventory and Hibob share in real time, so the people Hibob manages stay current in the system that runs finance and operations.
Hibob is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. DEAR Inventory runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.
Stacksync syncs Locations, Products, Stock levels, Sale orders in DEAR Inventory with Lifecycle, Documents, Named lists, People (Employees) in Hibob field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while DEAR Inventory keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.
Common use cases
- 01 Land orders, costs, and inventory movements in a warehouse for margin and stock-turn reporting.
- 02 Keep supplier and purchase order data aligned with the accounting system for accrual accuracy.
- 03 Two-way sync People (employee) profiles and Work records with a Postgres database so internal apps and directories read profiles in SQL while HR corrections flow back into Bob.
- 04 Auto-provision or deprovision accounts in an IdP, ticketing tool, or app database when Bob Lifecycle events fire employee joined or terminated.
Common sync patterns
Reporting lines drive approvals
Manager and reporting-hierarchy changes in Hibob keep expense and purchase approval chains in DEAR Inventory pointed at the right people.
Where Hibob runs payroll: labor cost in the books
Pay and compensation data from Hibob posts into DEAR Inventory as labor cost, so finance sees workforce spend without re-entering it by hand.
Where Hibob is the worker system of record: one employee master
When a worker is hired, moved, or offboarded in Hibob, the matching employee record in DEAR Inventory is created, updated, or deactivated, so the business system reflects the workforce as it actually is.
What you can sync between DEAR Inventory and Hibob
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.
| DEAR Inventory objects | Hibob objects | How this pairing syncs | |
|---|---|---|---|
| Locations Warehouses and bins that scope stock levels and fulfillment. | Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. | Locations is specific to DEAR Inventory and Work to Hibob — each maps to any object or custom field on the other side. | |
| Products SKU records with pricing, suppliers, and bill-of-material links; the master data most syncs start from. | Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. | Products is specific to DEAR Inventory and Salaries to Hibob — each maps to any object or custom field on the other side. | |
| Stock levels Per-location availability derived from inventory transactions; read-heavy in storefront syncs. | Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. | Stock levels is specific to DEAR Inventory and Time off to Hibob — each maps to any object or custom field on the other side. | |
| Sale orders Customer orders through their pick/pack/ship lifecycle; synced with storefronts and CRMs. | Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. | Sale orders is specific to DEAR Inventory and Lifecycle to Hibob — each maps to any object or custom field on the other side. | |
| Purchase orders Supplier orders and receiving records synced with accounting and planning tools. | Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. | Purchase orders is specific to DEAR Inventory and Documents to Hibob — each maps to any object or custom field on the other side. | |
| Customers Buyer records aligned with CRM and accounting counterparts. | Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. | Customers is specific to DEAR Inventory and Named lists to Hibob — each maps to any object or custom field on the other side. |
How changes propagate between DEAR Inventory and Hibob
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.
DEAR Inventory Hibob Sub-second propagation
DetectionDEAR Inventory notifies Stacksync of record changes through webhook events. Polling with modified-since filters.
DeliveryEach detected change is written to Hibob through its API, with automatic retries and rate-limit backoff.
Hibob DEAR Inventory 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 written to DEAR Inventory through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- DEAR Inventory: Subject to the platform's per-account API rate limits.
- 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.
What ships with DEAR Inventory ⇄ Hibob
Connect DEAR Inventory and Hibob for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DEAR Inventory–Hibob connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever DEAR Inventory or Hibob 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 DEAR Inventory or Hibob record.
Observability
Monitoring
Track your DEAR Inventory ⇄ Hibob sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between DEAR Inventory and Hibob.
How the DEAR Inventory and Hibob connectors work
DEAR Inventory
- Integration surface
- REST API
- Authentication
- Account ID plus application key sent as request headers
- Change detection
- Polling with modified-since filters; webhook notifications for sale and purchase events are available on subscriptions that include the Automation module
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's per-account API rate limits
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.
How it works
How to connect DEAR Inventory to Hibob — 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 DEAR Inventory and Hibob with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
DEAR Inventory
connected
Hibob
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the DEAR Inventory and Hibob 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 · DEAR Inventory ⇄ HibobCustomers 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.
DEAR Inventory HibobCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
DEAR Inventory and Hibob integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between DEAR Inventory and Hibob: authenticate both systems, choose the objects to sync (such as DEAR Inventory's Locations and Products), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the DEAR Inventory side: Locations, Products, Stock levels, Sale orders, plus custom fields where DEAR Inventory exposes them. On the Hibob side: Lifecycle, Documents, Named lists, People (Employees). 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 DEAR Inventory and Hibob: Reporting lines drive approvals; Where Hibob runs payroll: labor cost in the books; Where Hibob is the worker system of record: one employee master. Manager and reporting-hierarchy changes in Hibob keep expense and purchase approval chains in DEAR Inventory pointed at the right people.
-
DEAR Inventory: REST API. Authentication: Account ID plus application key sent as request headers. Hibob: 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
DEAR Inventory: Authentication uses a two-part credential, an account ID and an application key, passed as headers on every request. Hibob: The GET Read-all-company-employees and Read-by-ID endpoints are legacy; Bob steers reads to POST /people/search, which the docs rate-limit at 50 requests per minute. Stacksync's field mapping accounts for these differences between DEAR Inventory and Hibob without custom code.
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 408 integrations available for DEAR Inventory and Hibob.
Popular · 6 of 408
-
DEAR Inventory ⇄ Greenhouse -
DEAR Inventory ⇄ Jobvite -
DEAR Inventory ⇄ Lever -
Hibob ⇄ Epicor ERP -
Hibob ⇄ Extensiv (3PL Central) -
Hibob ⇄ Fishbowl Manufacturing
No integrations match .
