Real-time
Two-way sync
Changes in Hibob or Nimble instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ CRM
Hibob to Nimble integration — real-time, two-way sync
Keep Hibob and Nimble 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 Nimble
Keep the people who own accounts in Nimble 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.
Nimble 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 Notes, Tags, Custom fields, Contacts in Nimble with Employment, Work, Salaries, Time off 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 Nimble keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Feed Nimble activity and task data into reporting dashboards without manual CSV exports.
- 02 Sync Nimble contacts and companies into Postgres so ops teams can query socially enriched profile 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
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 Nimble, 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 Nimble, 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 Nimble update to match, so pipeline stays with the right owner.
What you can sync between Hibob and Nimble
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 | Nimble objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Activities Calls, events, and interaction history used for engagement reporting outside Nimble | People (Employees) is specific to Hibob and Activities to Nimble — 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. | Notes Free-text records attached to contacts, replicated for a complete account timeline | Employment is specific to Hibob and Notes to Nimble — 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. | Tags Segmentation labels that map to list membership or filters in downstream systems | Work is specific to Hibob and Tags to Nimble — 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. | Custom fields Account-defined contact attributes that carry enrichment or internal identifiers | Salaries is specific to Hibob and Custom fields to Nimble — 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. | Contacts Person records with multi-value fields for email, phone, and social profiles; the primary sync entity | Time off is specific to Hibob and Contacts to Nimble — 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. | Companies Stored as contact records with a company record type, so they sync through the same contacts resource | Lifecycle is specific to Hibob and Companies to Nimble — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and Nimble
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 Nimble 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 Nimble through its API, with automatic retries and rate-limit backoff.
Nimble Hibob Interval-based propagation
DetectionStacksync polls Nimble for changes on an incremental schedule, reading only records changed since the previous pass. Polling on record modification 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.
- Nimble: Subject to per-account API request quotas.
What ships with Hibob ⇄ Nimble
Connect Hibob and Nimble for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Nimble connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or Nimble 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 Nimble record.
Observability
Monitoring
Track your Hibob ⇄ Nimble 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 Nimble.
How the Hibob and Nimble 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.
Nimble
- Integration surface
- REST API (JSON)
- Authentication
- API key; OAuth 2.0 available for registered applications
- Change detection
- polling on record modification timestamps
- Capabilities
- read · write
- Rate limits
- subject to per-account API request quotas
How it works
How to connect Hibob to Nimble — 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 Nimble 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
Nimble
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and Nimble 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 ⇄ NimbleCustomers 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 NimbleCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and Nimble integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and Nimble: authenticate both systems, choose the objects to sync (such as Hibob's People (Employees) and Employment), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Nimble: Where Hibob tracks people the business also engages: contacts stay in sync; New team members provisioned when they are hired; Ownership and territory follow the org chart. A person recorded in Hibob, such as a candidate or applicant, can create or update the matching contact in Nimble, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
-
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. Nimble: REST API (JSON). Authentication: API key; OAuth 2.0 available for registered applications. Stacksync manages authentication, retries, and rate limits on both sides.
-
Nimble: Nimble stores people and companies as contact records distinguished by record type, so both entity types flow through the same contacts resource. Hibob: The employee.updated webhook flags which fields changed rather than sending the full record, so Bob recommends an API call for complete data; deleting a table entry triggers no webhook because Bob has no table-entry deletion event. Stacksync's field mapping accounts for these differences between Hibob and Nimble 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 Nimble records are not retained after a sync operation.
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 419 integrations available for Hibob and Nimble.
Popular · 7 of 419
-
Hibob ⇄ Intercom -
Hibob ⇄ Kommo -
Hibob ⇄ Kustomer -
Hibob ⇄ Nutshell -
Nimble ⇄ Ukg Ready -
Nimble ⇄ Success Factors -
Nimble ⇄ Ceridian Dayforce
No integrations match .
