Real-time
Two-way sync
Changes in Close or Hibob instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Human resources
Close to Hibob integration — real-time, two-way sync
Keep Close 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 Close and Hibob
Keep the people who own accounts in Close 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.
Close 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 Custom Fields, Users, Smart Views, Leads in Close 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 Hibob stays authoritative on roles and org structure while Close keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.
- 02 Keep Close contacts aligned with a marketing automation platform so outreach lists stay current.
- 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
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.
Where Hibob tracks people the business also engages: contacts stay in sync
A person recorded in Hibob, such as a candidate or applicant, can create or update the matching contact in Close, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
New team members provisioned when they are hired
When Hibob records a new hire, a matching user or owner is created in Close, so a new rep can start working accounts without waiting on a manual setup ticket.
What you can sync between Close 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.
| Close objects | Hibob objects | How this pairing syncs | |
|---|---|---|---|
| Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. | Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. | Custom Fields is specific to Close and Employment to Hibob — each maps to any object or custom field on the other side. | |
| Users Sales reps referenced as owners on leads, opportunities, and activities. | Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. | Users is specific to Close and Work to Hibob — each maps to any object or custom field on the other side. | |
| Smart Views Saved lead searches that can scope which records a segment-based sync pulls. | Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. | Smart Views is specific to Close and Salaries to Hibob — each maps to any object or custom field on the other side. | |
| Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. | Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. | Leads is specific to Close and Time off to Hibob — each maps to any object or custom field on the other side. | |
| Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. | Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. | Contacts is specific to Close and Lifecycle to Hibob — each maps to any object or custom field on the other side. | |
| Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. | Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. | Opportunities is specific to Close and Documents to Hibob — each maps to any object or custom field on the other side. |
How changes propagate between Close 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.
Close Hibob Sub-second propagation
DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.
DeliveryEach detected change is written to Hibob through its API, with automatic retries and rate-limit backoff.
Hibob Close 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 Close through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Close: Subject to per-endpoint rate limits communicated in response headers.
- 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 Close ⇄ Hibob
Connect Close and Hibob for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Close–Hibob connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Close 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 Close or Hibob record.
Observability
Monitoring
Track your Close ⇄ Hibob sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Close and Hibob.
How the Close and Hibob connectors work
Close
- Integration surface
- REST API
- Authentication
- API key (sent via HTTP Basic auth)
- Change detection
- Webhook subscriptions for record events, with polling on date_updated fields for backfills
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-endpoint rate limits communicated in response headers
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 Close 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 Close 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.
Close
connected
Hibob
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Close 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 · Close ⇄ 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.
Close HibobCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Close and Hibob integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Close and Hibob: authenticate both systems, choose the objects to sync (such as Close's Custom Fields and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Close side: Custom Fields, Users, Smart Views, Leads, plus custom fields where Close 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 Close and Hibob: One directory of people; Where Hibob tracks people the business also engages: contacts stay in sync; New team members provisioned when they are hired. 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.
-
Close: REST API. Authentication: API key (sent via HTTP Basic auth). 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.
-
Close: Close's data model is lead-centric: the Lead is a company-level record, and contacts, opportunities, and activities all hang off it, unlike CRMs that treat accounts and contacts as separate top-level objects. 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 Close 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 529 integrations available for Close and Hibob.
Popular · 6 of 529
-
Close ⇄ Success Factors -
Close ⇄ Ceridian Dayforce -
Close ⇄ D2l Brightspace -
Hibob ⇄ Copper CRM -
Hibob ⇄ Creatio CRM -
Hibob ⇄ Folk CRM
No integrations match .
