Real-time
Two-way sync
Changes in Hibob or Twenty CRM instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ CRM
Hibob to Twenty CRM integration — real-time, two-way sync
Keep Hibob and Twenty CRM 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 Twenty CRM
Keep the people who own accounts in Twenty CRM 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.
Twenty CRM 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 People, Companies, Opportunities, Tasks in Twenty CRM with Work, Salaries, Time off, Lifecycle 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 Twenty CRM keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Run a continuous sync from a legacy CRM into Twenty during a migration so both systems stay usable through cutover.
- 02 Two-way sync of People and Companies between Twenty and a production Postgres database so engineers can query CRM data with SQL.
- 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
Ownership and territory follow the org chart
When a person changes team, manager, or region in Hibob, their accounts and territory assignments in Twenty CRM 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 Twenty CRM is flagged or deactivated, so former employees do not keep CRM access after their last day.
One directory of people
A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
What you can sync between Hibob and Twenty CRM
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 | Twenty CRM objects | How this pairing syncs | |
|---|---|---|---|
| Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. | Tasks To-dos linked to people, companies, or deals. | Documents is specific to Hibob and Tasks to Twenty CRM — 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-form notes attached to records, useful for mirroring activity from other tools. | Named lists is specific to Hibob and Notes to Twenty CRM — 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 Objects User-defined objects created in Twenty's data model settings, addressable through the same APIs as standard objects. | People (Employees) is specific to Hibob and Custom Objects to Twenty CRM — 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. | Attachments Files linked to records. | Employment is specific to Hibob and Attachments to Twenty CRM — 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. | Workspace Members User accounts used for record ownership and assignment mapping. | Work is specific to Hibob and Workspace Members to Twenty CRM — 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. | People Individual contact records with emails, phones, and company links; a core target for contact syncs. | Salaries is specific to Hibob and People to Twenty CRM — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and Twenty CRM
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 Twenty CRM 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 Twenty CRM through its API, with automatic retries and rate-limit backoff.
Twenty CRM Hibob Sub-second propagation
DetectionTwenty CRM notifies Stacksync of record changes through webhook events. Webhooks on record create, update, and delete events, or polling on record update timestamps.
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.
- Twenty CRM: Subject to the platform's API rate limits; self-hosted deployments control their own limits.
What ships with Hibob ⇄ Twenty CRM
Connect Hibob and Twenty CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Twenty CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or Twenty CRM 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 Twenty CRM record.
Observability
Monitoring
Track your Hibob ⇄ Twenty CRM 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 Twenty CRM.
How the Hibob and Twenty CRM 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.
Twenty CRM
- Integration surface
- GraphQL and REST APIs
- Authentication
- API key
- Change detection
- Webhooks on record create, update, and delete events, or polling on record update timestamps
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits; self-hosted deployments control their own limits.
How it works
How to connect Hibob to Twenty CRM — 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 Twenty CRM 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
Twenty CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and Twenty CRM 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 ⇄ Twenty CRMCustomers 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 Twenty CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and Twenty CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and Twenty CRM: 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.
-
Yes — Stacksync ships production-grade connectors for both Hibob and Twenty CRM. 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 Twenty CRM: Webhooks on record create, update, and delete events, or polling on record update timestamps. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Twenty CRM side: People, Companies, Opportunities, Tasks, plus custom fields where Twenty CRM exposes them. On the Hibob side: Work, Salaries, Time off, Lifecycle. 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 Twenty CRM: Ownership and territory follow the org chart; Deactivate access when someone leaves; One directory of people. When a person changes team, manager, or region in Hibob, their accounts and territory assignments in Twenty CRM update to match, so pipeline stays with the right owner.
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 435 integrations available for Hibob and Twenty CRM.
Popular · 7 of 435
-
Hibob ⇄ Gorgias -
Hibob ⇄ Infor CRM -
Hibob ⇄ Insightly -
Hibob ⇄ Intercom -
Twenty CRM ⇄ Ceridian Dayforce -
Twenty CRM ⇄ Oracle Fusion Cloud HCM -
Twenty CRM ⇄ Smartrecruiters
No integrations match .
