Odoo and BambooHR integration

What moves between them

Employee records flow from Odoo to BambooHR on a schedule you define, typically daily or weekly. ml-connector matches employees by email address, so an email change in either system requires manual reconciliation. Job title, department, and compensation are synced from Odoo to BambooHR to keep HR systems current with organizational changes. When BambooHR webhooks are enabled, employment status changes (termination, rehire) flow back to Odoo, allowing finance systems to align headcount and cost allocations. Reference data such as departments and job codes are kept in sync so payroll allocations land on valid organizational dimensions.

How ml-connector handles it

ml-connector stores both API credentials encrypted and retrieves Odoo employee records using JSON-2 API calls filtered by write_date to find only changed records since the last sync. It then queries BambooHR to find matching employees by email, and updates or creates employee records with the Odoo job title, department, and compensation data. BambooHR's OAuth 2.0 token is refreshed automatically when it expires (1 hour), and ml-connector validates webhook signatures using SHA-256 HMAC to ensure incoming employee changes are authentic. When BambooHR webhooks signal an employee update, ml-connector fetches the full employee record and propagates employment status and compensation back to Odoo, allowing two-way sync. Email is the stable match key - if email changes in either system without corresponding update in the other, the employee record creates a duplicate until manually reconciled. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized manufacturing company runs Odoo for accounting, inventory, and purchasing, and uses BambooHR for HR, payroll, and benefits administration across three locations. Before the integration, the HR manager manually exported employee lists from Odoo every month and uploaded changes to BambooHR by hand, causing delays when new hires started or roles changed. The finance team in Odoo had stale headcount data and struggled to allocate labor costs to the right departments and cost centers. With Odoo and BambooHR connected, employee data syncs automatically so BambooHR reflects new hires and role changes within hours, and finance in Odoo stays current with real organizational structure. The manual export-and-upload step is gone, and both teams see the same employee roster.

What you can do

• •Sync employees from Odoo to BambooHR, matching by email address and updating job title, department, and compensation.
• •Monitor BambooHR webhooks to detect employment status changes and propagate terminations and rehires back to Odoo.
• •Authenticate Odoo with API key and BambooHR with OAuth 2.0, refreshing BambooHR's access token automatically when it expires.
• •Poll Odoo on a schedule you control using write_date filtering to fetch only changed records since the last sync.
• •Track which records have been synced and maintain a full audit trail so any record can be replayed if a downstream call fails.

Questions

Which direction does employee data move between Odoo and BambooHR?

Employee records flow primarily from Odoo to BambooHR so job title, department, and compensation stay current in your HR system. When BambooHR webhooks are enabled, employment status changes such as terminations and rehires flow back to Odoo so finance systems stay aware of headcount changes and can adjust cost allocations. Email is the match key, so email changes in either system without a corresponding update in the other create duplicate records.

How does ml-connector handle Odoo's lack of native webhooks?

ml-connector polls the Odoo API on a schedule you define, typically daily or weekly, using write_date filtering to fetch only changed records since the last sync. This avoids constant querying and keeps API usage low. BambooHR webhooks are optional - when enabled, they notify ml-connector of employee updates within minutes, allowing faster two-way sync. Without webhooks, changes in BambooHR will be detected on the next Odoo polling cycle.

What happens if an employee email address changes?

Email is the stable match key between Odoo and BambooHR. If an employee email changes in one system without a corresponding update in the other, ml-connector will treat the old and new email as separate employees and create a duplicate record. This requires manual reconciliation in both systems. Planning email changes across both systems at the same time, or updating both systems first before re-enabling the sync, avoids duplicates.