Real-time
Two-way sync
Changes in Freshworks CRM or Hibob instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Human resources
Freshworks CRM to Hibob integration — real-time, two-way sync
Keep Freshworks CRM 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 Freshworks CRM and Hibob
Keep the people who own accounts in Freshworks 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.
Freshworks 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 Tasks, Appointments, Sales activities, Lists in Freshworks 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 Freshworks CRM keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Keep list membership aligned with segments computed in the warehouse.
- 02 Mirror deal and activity data into a Postgres database that internal tools query directly.
- 03 Auto-provision or deprovision accounts in an IdP, ticketing tool, or app database when Bob Lifecycle events fire employee joined or terminated.
- 04 Push Salaries and Variable Pay from Bob into a payroll provider or warehouse each pay cycle, using the Payroll-permitted service user.
Common sync patterns
Deactivate access when someone leaves
When Hibob marks a worker as departed, the matching user in Freshworks 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.
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 Freshworks CRM, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
What you can sync between Freshworks CRM 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.
| Freshworks CRM objects | Hibob objects | How this pairing syncs | |
|---|---|---|---|
| Appointments Meeting records readable for activity reporting. | Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. | Appointments is specific to Freshworks CRM and Work to Hibob — each maps to any object or custom field on the other side. | |
| Sales activities Logged activity types used in engagement and productivity analysis. | Salaries Compensation history at /people/{id}/salaries; full CRUD but gated behind the Payroll permission on the service user. | Sales activities is specific to Freshworks CRM and Salaries to Hibob — each maps to any object or custom field on the other side. | |
| Lists Contact list membership synced against segments computed in a warehouse. | Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. | Lists is specific to Freshworks CRM and Time off to Hibob — each maps to any object or custom field on the other side. | |
| Notes Context records attached to contacts, accounts, and deals. | Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. | Notes is specific to Freshworks CRM and Lifecycle to Hibob — each maps to any object or custom field on the other side. | |
| Contacts Unified sales-and-marketing person records; the core entity for bidirectional syncs. | Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. | Contacts is specific to Freshworks CRM and Documents to Hibob — each maps to any object or custom field on the other side. | |
| Accounts Company records kept consistent with ERP and billing systems. | Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. | Accounts is specific to Freshworks CRM and Named lists to Hibob — each maps to any object or custom field on the other side. |
How changes propagate between Freshworks CRM 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.
Freshworks CRM Hibob Sub-second propagation
DetectionFreshworks CRM notifies Stacksync of record changes through webhook events. Polling with updated-at filters.
DeliveryEach detected change is written to Hibob through its API, with automatic retries and rate-limit backoff.
Hibob Freshworks 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 Freshworks CRM through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Freshworks CRM: Subject to per-account API rate limits that vary by plan.
- 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 Freshworks CRM ⇄ Hibob
Connect Freshworks CRM and Hibob for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Freshworks CRM–Hibob connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Freshworks CRM 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 Freshworks CRM or Hibob record.
Observability
Monitoring
Track your Freshworks CRM ⇄ Hibob sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Freshworks CRM and Hibob.
How the Freshworks CRM and Hibob connectors work
Freshworks CRM
- Integration surface
- REST API
- Authentication
- API key sent as a Token authorization header
- Change detection
- Polling with updated-at filters; outbound webhooks can be configured through workflow automations
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that vary by plan
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 Freshworks CRM 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 Freshworks CRM 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.
Freshworks CRM
connected
Hibob
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Freshworks CRM 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 · Freshworks CRM ⇄ 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.
Freshworks CRM HibobCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Freshworks CRM and Hibob integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Freshworks CRM and Hibob: authenticate both systems, choose the objects to sync (such as Freshworks CRM's Appointments and Sales activities), 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 Freshworks CRM and Hibob: Deactivate access when someone leaves; One directory of people; Where Hibob tracks people the business also engages: contacts stay in sync. When Hibob marks a worker as departed, the matching user in Freshworks CRM is flagged or deactivated, so former employees do not keep CRM access after their last day.
-
Freshworks CRM: REST API. Authentication: API key sent as a Token authorization header. 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.
-
Freshworks CRM: Contacts and accounts expose lifecycle stages and custom fields through the API, so one record serves both sales and marketing workflows. Hibob: Service User permissions are granular and per-category (People, Payroll, Documents); a request fails unless that category is explicitly granted in Bob admin. Stacksync's field mapping accounts for these differences between Freshworks CRM and Hibob 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 Freshworks CRM and Hibob 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 522 integrations available for Freshworks CRM and Hibob.
Popular · 8 of 522
-
Freshworks CRM ⇄ Smartrecruiters -
Freshworks CRM ⇄ Ukg Pro -
Freshworks CRM ⇄ Greenhouse -
Freshworks CRM ⇄ Jobvite -
Hibob ⇄ Freshsales -
Hibob ⇄ Gladly -
Hibob ⇄ Gorgias -
Hibob ⇄ Infor CRM
No integrations match .
