Skip to content
Human resources ⇄ ERP

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

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

Sync the workers, org structure, and cost centers that Odoo and Hibob share in real time, so the people Hibob manages stay current in the system that runs finance and operations.

Hibob is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. Odoo runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.

Stacksync syncs Invoices (account.move), Products (product.template / product.product), CRM Leads (crm.lead), Purchase Orders (purchase.order) in Odoo with Time off, Lifecycle, Documents, Named lists in Hibob field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while Odoo keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • 01 Keep product and price list data aligned between Odoo and storefronts or marketplaces.
  • 02 Sync employee records from an HR system of record into Odoo for expense and timesheet workflows.
  • 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

Where Hibob is the worker system of record: one employee master

When a worker is hired, moved, or offboarded in Hibob, the matching employee record in Odoo is created, updated, or deactivated, so the business system reflects the workforce as it actually is.

New hires ready to transact in Odoo

A new person set up in Hibob becomes an employee record in Odoo in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.

One org structure

Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Odoo roll up to the same structure Hibob maintains.

What you can sync between Hibob and Odoo

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 Odoo objects How this pairing syncs
Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. Projects and Tasks (project.project / project.task) Work items synced with external project tools. Employment is specific to Hibob and Projects and Tasks (project.project / project.task) to Odoo — 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. Contacts (res.partner) The unified person/company record used across sales, invoicing, and purchasing; the anchor for CRM syncs. Work is specific to Hibob and Contacts (res.partner) to Odoo — 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. Sales Orders (sale.order) Quotations and confirmed orders synced with e-commerce and external CRMs. Salaries is specific to Hibob and Sales Orders (sale.order) to Odoo — 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. Invoices (account.move) Customer invoices and journal entries synced with accounting and reporting tools. Time off is specific to Hibob and Invoices (account.move) to Odoo — 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. Products (product.template / product.product) Catalog and variant data distributed to storefronts and quoting tools. Lifecycle is specific to Hibob and Products (product.template / product.product) to Odoo — each maps to any object or custom field on the other side.
Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. CRM Leads (crm.lead) Leads and opportunities synced with marketing and enrichment systems. Documents is specific to Hibob and CRM Leads (crm.lead) to Odoo — each maps to any object or custom field on the other side.

How changes propagate between Hibob and Odoo

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

Odoo Hibob Sub-second propagation

DetectionOdoo notifies Stacksync of record changes through webhook events. Polling on the write_date timestamp every record carries.

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.
  • Odoo: Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits.
What ships with Hibob ⇄ Odoo

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Hibob ⇄ Odoo 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 Odoo.

How the Hibob and Odoo 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.
Hibob setup guide

Odoo

Integration surface
XML-RPC and JSON-RPC external API exposing the full ORM (search_read, create, write, unlink)
Authentication
Database user credentials or per-user API keys
Change detection
Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules
Capabilities
read · write · webhooks
Rate limits
Self-hosted instances have no fixed rate limits; Odoo Online is subject to the platform's fair-use limits
How it works

How to connect Hibob to Odoo — 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 Hibob and Odoo 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
    Hibob connected
    Odoo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Hibob and Odoo 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 · Hibob ⇄ Odoo
    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
    Hibob Odoo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Hibob and Odoo 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 520 integrations available for Hibob and Odoo.

Popular · 8 of 520
All Hibob integrations All Odoo 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