Real-time
Two-way sync
Changes in Hibob or Salesloft instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ CRM
Hibob to Salesloft integration — real-time, two-way sync
Keep Hibob and Salesloft 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 Salesloft
Keep the people who own accounts in Salesloft 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.
Salesloft 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 Cadence Memberships, Emails, Calls, Tasks in Salesloft with People (Employees), Employment, Work, Salaries 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 Salesloft keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Auto-enroll leads into cadences when a row in an enrichment database meets a scoring condition.
- 02 Write email and call activity back to the CRM or a Postgres table for a complete engagement timeline.
- 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
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 Salesloft, 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 Salesloft, so a new rep can start working accounts without waiting on a manual setup ticket.
What you can sync between Hibob and Salesloft
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 | Salesloft 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. | People Prospect records with contact data and CRM ID mappings, the primary sync target. | People (Employees) is specific to Hibob and People to Salesloft — 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. | Accounts Company records mirrored from the CRM for account-based workflows. | Employment is specific to Hibob and Accounts to Salesloft — 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. | Cadences Multi-step outreach sequences that people are enrolled in and reported on. | Work is specific to Hibob and Cadences to Salesloft — 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. | Cadence Memberships Enrollment records linking a person to a cadence step and status. | Salaries is specific to Hibob and Cadence Memberships to Salesloft — 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. | Emails Sent and received email activity with engagement metadata, synced out for analytics. | Time off is specific to Hibob and Emails to Salesloft — 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. | Calls Logged call activity with dispositions and recordings metadata. | Lifecycle is specific to Hibob and Calls to Salesloft — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and Salesloft
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 Salesloft 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 Salesloft through its API, with automatic retries and rate-limit backoff.
Salesloft Hibob Sub-second propagation
DetectionSalesloft notifies Stacksync of record changes through webhook events. Webhook event subscriptions plus polling on updated_at 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.
- Salesloft: Subject to the platform's per-minute API rate limits.
What ships with Hibob ⇄ Salesloft
Connect Hibob and Salesloft for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Salesloft connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or Salesloft 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 Salesloft record.
Observability
Monitoring
Track your Hibob ⇄ Salesloft 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 Salesloft.
How the Hibob and Salesloft 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.
Salesloft
- Integration surface
- REST API (v2)
- Authentication
- OAuth 2.0
- Change detection
- Webhook event subscriptions plus polling on updated_at timestamps
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's per-minute API rate limits
How it works
How to connect Hibob to Salesloft — 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 Salesloft 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
Salesloft
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and Salesloft 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 ⇄ SalesloftCustomers 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 SalesloftCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and Salesloft integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and Salesloft: 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.
-
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 Salesloft: Webhook event subscriptions plus polling on updated_at timestamps. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Salesloft side: Cadence Memberships, Emails, Calls, Tasks, plus custom fields where Salesloft exposes them. On the Hibob side: People (Employees), Employment, Work, Salaries. 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 Salesloft: 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.
-
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. Salesloft: REST API (v2). Authentication: OAuth 2.0. Stacksync manages authentication, retries, and rate limits on both sides.
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 504 integrations available for Hibob and Salesloft.
Popular · 8 of 504
-
Hibob ⇄ DealCloud -
Hibob ⇄ Chorusai -
Hibob ⇄ Clari -
Hibob ⇄ Dun And Bradstreet -
Salesloft ⇄ Oracle Fusion Cloud HCM -
Salesloft ⇄ Smartrecruiters -
Salesloft ⇄ Ukg Pro -
Salesloft ⇄ Greenhouse
No integrations match .
