Real-time
Two-way sync
Changes in Hibob or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ CRM
Hibob to Kustomer integration — real-time, two-way sync
Keep Hibob and Kustomer 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 Kustomer
Keep the people who own accounts in Kustomer in step with the workforce records in Hibob, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.
Kustomer runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Hibob. Hibob is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.
Stacksync syncs Tags, Notes, Customers, Conversations in Kustomer with Documents, Named lists, People (Employees), Employment in Hibob field by field, in real time, and in both directions. You decide which system owns which fields, so Hibob stays authoritative on roles and org structure while Kustomer keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Push order and shipment records from commerce systems into Kustomer custom objects so agents answer order-status questions without switching tools
- 02 Mirror conversations and satisfaction data into a warehouse for support analytics and agent performance reporting
- 03 Mirror Work data (department, site, manager, title) into an org-chart or reporting warehouse for headcount and structure analysis.
- 04 Sync Time off requests and who's-out data into a scheduling or workforce-planning database for coverage and capacity reporting.
Common sync patterns
New team members provisioned when they are hired
When Hibob records a new hire, a matching user or owner is created in Kustomer, so a new rep can start working accounts without waiting on a manual setup ticket.
Ownership and territory follow the org chart
When a person changes team, manager, or region in Hibob, their accounts and territory assignments in Kustomer update to match, so pipeline stays with the right owner.
Deactivate access when someone leaves
When Hibob marks a worker as departed, the matching user in Kustomer is flagged or deactivated, so former employees do not keep CRM access after their last day.
What you can sync between Hibob and Kustomer
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 | Kustomer objects | How this pairing syncs | |
|---|---|---|---|
| Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. | Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. | Employment is specific to Hibob and Custom Objects (Klasses) to Kustomer — each maps to any object or custom field on the other side. | |
| Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. | Users Agent records map conversation ownership to people in other systems. | Work is specific to Hibob and Users to Kustomer — each maps to any object or custom field on the other side. | |
| Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. | Teams Team assignments support routing parity and reporting. | Salaries is specific to Hibob and Teams to Kustomer — 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. | Tags Labels on conversations and customers sync for categorization and analytics. | Time off is specific to Hibob and Tags to Kustomer — 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. | Notes Internal annotations carry context alongside synced conversations. | Lifecycle is specific to Hibob and Notes to Kustomer — 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. | Customers The central record whose timeline aggregates every interaction; external attributes sync onto it. | Documents is specific to Hibob and Customers to Kustomer — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and Kustomer
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 Kustomer 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 Kustomer through its API, with automatic retries and rate-limit backoff.
Kustomer Hibob Sub-second propagation
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.
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.
- Kustomer: Subject to the platform's API rate limits.
What ships with Hibob ⇄ Kustomer
Connect Hibob and Kustomer for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Kustomer connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or Kustomer 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 Kustomer record.
Observability
Monitoring
Track your Hibob ⇄ Kustomer 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 Kustomer.
How the Hibob and Kustomer 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.
Kustomer
- Integration surface
- REST API
- Authentication
- API key used as a bearer token, scoped by role
- Change detection
- Outbound webhooks on record events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
How it works
How to connect Hibob to Kustomer — 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 Kustomer 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
Kustomer
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and Kustomer 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 ⇄ KustomerCustomers 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 KustomerCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and Kustomer integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and Kustomer: authenticate both systems, choose the objects to sync (such as Hibob's Employment and Work), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Hibob and Kustomer: New team members provisioned when they are hired; Ownership and territory follow the org chart; Deactivate access when someone leaves. When Hibob records a new hire, a matching user or owner is created in Kustomer, so a new rep can start working accounts without waiting on a manual setup ticket.
-
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. Kustomer: REST API. Authentication: API key used as a bearer token, scoped by role. Stacksync manages authentication, retries, and rate limits on both sides.
-
Kustomer: API keys are issued as role-scoped bearer tokens, so integration access can be limited to the specific object types a sync touches. Hibob: Historical tables key entries by effectiveDate while non-historical tables key by id, which sync engines must handle when reconciling changes. Stacksync's field mapping accounts for these differences between Hibob and Kustomer 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 Hibob and Kustomer records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Hibob and Kustomer connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Hibob–Kustomer integration in-house.
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 418 integrations available for Hibob and Kustomer.
Popular · 8 of 418
-
Hibob ⇄ Gladly -
Hibob ⇄ Gorgias -
Hibob ⇄ Infor CRM -
Hibob ⇄ Insightly -
Kustomer ⇄ Oracle Fusion Cloud HCM -
Kustomer ⇄ Smartrecruiters -
Kustomer ⇄ Ukg Pro -
Kustomer ⇄ Greenhouse
No integrations match .
