Real-time
Two-way sync
Changes in Hibob or Kommo instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ CRM
Hibob to Kommo integration — real-time, two-way sync
Keep Hibob and Kommo 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 Kommo
Keep the people who own accounts in Kommo 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.
Kommo 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 Companies, Pipelines & Statuses, Tasks, Notes in Kommo with Salaries, Time off, Lifecycle, Documents 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 Kommo keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Replicate Kommo leads and contacts into a database or warehouse for reporting beyond built-in dashboards
- 02 Push web form and product signups into Kommo pipelines as they are submitted so messenger-based follow-up starts quickly
- 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
New team members provisioned when they are hired
When Hibob records a new hire, a matching user or owner is created in Kommo, 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 Kommo 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 Kommo is flagged or deactivated, so former employees do not keep CRM access after their last day.
What you can sync between Hibob and Kommo
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 | Kommo objects | How this pairing syncs | |
|---|---|---|---|
| Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. | Tasks Follow-up records keep rep activity consistent across systems. | Documents is specific to Hibob and Tasks to Kommo — 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. | Notes Free-text and system notes attach context to synced leads and contacts. | Named lists is specific to Hibob and Notes to Kommo — 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. | Custom Fields Per-entity custom fields hold data written from external databases and enrichment. | People (Employees) is specific to Hibob and Custom Fields to Kommo — each maps to any object or custom field on the other side. | |
| Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. | Users Account users map lead ownership to people in other systems. | Employment is specific to Hibob and Users to Kommo — 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. | Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. | Work is specific to Hibob and Chats to Kommo — 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. | Leads The central pipeline record; external signups and form fills sync in as leads. | Salaries is specific to Hibob and Leads to Kommo — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and Kommo
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 Kommo 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 Kommo through its API, with automatic retries and rate-limit backoff.
Kommo Hibob Sub-second propagation
DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update 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.
- Kommo: Subject to per-account request rate limits.
What ships with Hibob ⇄ Kommo
Connect Hibob and Kommo for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Kommo connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or Kommo 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 Kommo record.
Observability
Monitoring
Track your Hibob ⇄ Kommo 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 Kommo.
How the Hibob and Kommo 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.
Kommo
- Integration surface
- REST API
- Authentication
- OAuth 2.0 with refresh tokens
- Change detection
- Webhooks on record add and update events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account request rate limits
How it works
How to connect Hibob to Kommo — 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 Kommo 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
Kommo
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and Kommo 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 ⇄ KommoCustomers 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 KommoCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and Kommo integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and Kommo: authenticate both systems, choose the objects to sync (such as Hibob's Documents and Named lists), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Kommo side: Companies, Pipelines & Statuses, Tasks, Notes, plus custom fields where Kommo exposes them. On the Hibob side: Salaries, Time off, Lifecycle, Documents. 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 Kommo: 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 Kommo, 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. Kommo: REST API. Authentication: OAuth 2.0 with refresh tokens. Stacksync manages authentication, retries, and rate limits on both sides.
-
Kommo: Kommo is the former amoCRM, and its data model centers on leads moving through configurable pipelines and statuses, with contacts and companies linked to each lead. 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 Kommo 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 518 integrations available for Hibob and Kommo.
Popular · 8 of 518
-
Hibob ⇄ Salesforce -
Hibob ⇄ HubSpot -
Hibob ⇄ Microsoft Dynamics 365 Sales -
Hibob ⇄ Attio -
Kommo ⇄ Ceridian Dayforce -
Kommo ⇄ D2l Brightspace -
Kommo ⇄ Oracle Fusion Cloud HCM -
Kommo ⇄ Smartrecruiters
No integrations match .
