Skip to content
CRM ⇄ Human resources

Clari to Hibob integration — real-time, two-way sync

Keep Clari 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 Clari and Hibob

Keep the people who own accounts in Clari 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.

Clari 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 Activity (Capture), Account field extensions, Opportunity field extensions, Audit Events in Clari 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 Clari keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Pull Activity (Capture) meetings and emails, mapped to their accounts and opportunities, into a database for coverage and engagement analysis.
  • 02 Write warehouse-computed health scores and usage metrics onto Clari Opportunity records as field extensions via the ingest API so deal reviews show product signals.
  • 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 Clari 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 Clari 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 Clari 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.

Clari objects Hibob objects How this pairing syncs
Account field extensions External data points written onto Account records through the ingest API in initial or incremental mode; requires an apikey plus a partnerkey. Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. Account field extensions is specific to Clari and Time off to Hibob — each maps to any object or custom field on the other side.
Opportunity field extensions Warehouse-computed fields pushed onto Opportunity records via the ingest API; up to 100 records per request or 10MB bulk files. Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Opportunity field extensions is specific to Clari and Lifecycle to Hibob — each maps to any object or custom field on the other side.
Audit Events User edits and system events exported with filtering by actor, session, and date range; read-only feed for change tracking and compliance. Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. Audit Events is specific to Clari and Documents to Hibob — each maps to any object or custom field on the other side.
Forecast Exported per forecast tab and fiscal period via async jobs; includes submitted forecast calls, updates, manager adjustments, and CRM totals. Read-only. Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Forecast is specific to Clari and Named lists to Hibob — each maps to any object or custom field on the other side.
Quota Quota and quota-history values exported alongside forecast data, scoped by fiscal quarter; read-only, useful for warehouse attainment reporting. 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. Quota is specific to Clari and People (Employees) to Hibob — each maps to any object or custom field on the other side.
Opportunities Retrieved synchronously by ID from GET /opportunity (up to 100 IDs per call) with Clari CRM scoring and field-change history; read-only, mirroring the CRM opportunity Clari sits on. Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. Opportunities is specific to Clari and Employment to Hibob — each maps to any object or custom field on the other side.

How changes propagate between Clari 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.

Clari Hibob Interval-based propagation

DetectionStacksync polls Clari for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reads run as asynchronous export jobs (submit export, poll job status, download results).

DeliveryEach detected change is written to Hibob through its API, with automatic retries and rate-limit backoff.

Hibob Clari 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 Clari through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Clari: Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.
  • 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 Clari ⇄ Hibob

Connect Clari and Hibob for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Clari–Hibob connection.

Real-time

Two-way sync

Changes in Clari or Hibob instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Clari 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 Clari or Hibob record.

Observability

Monitoring

Track your Clari ⇄ Hibob sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Clari and Hibob.

How the Clari and Hibob connectors work

Clari

Integration surface
REST APIs on api.clari.com - Export API (v4, asynchronous bulk jobs for forecast, quota, activity, and audit) and Ingest API (v2, field extensions); Opportunity reads are synchronous via GET /opportunity
Authentication
API token in the apikey header, generated per user in Settings; ingest/partner endpoints also require a partnerkey header, and Copilot endpoints require X-Api-Key and X-Api-Password
Change detection
Polling — reads run as asynchronous export jobs (submit export, poll job status, download results); the ingest API supports an incremental mode for regular field updates. No webhooks.
Capabilities
read · write
Rate limits
Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.

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.
Hibob setup guide
How it works

How to connect Clari 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.

  1. 01

    Connect your apps

    Authenticate Clari 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Clari connected
    Hibob connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Clari 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Clari ⇄ Hibob
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Clari Hibob
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Clari and Hibob integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 422 integrations available for Clari and Hibob.

Popular · 7 of 422
All Clari integrations All Hibob integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own