Employment Hero Onboarding Sync
Pull onboarding workflows, employee goals and contractor details from the Employment Hero people platform into Odoo, with field mappings and sync jobs you tune from the screen.
Store price is USD 117 all-in: installing this also pulls the 2 paid ERP Heritage modules it depends on.
Why this module
Employment Hero Onboarding Sync
Models Community does not ship
Odoo Community has no onboarding or goal record. This module adds two clean ones, populated from the Employment Hero people platform and linked to the matching employee.
Mappings and jobs are data
Endpoints, field mappings and sync jobs ship as editable records. Point a source path at your own payload shape and adjust the job from the screen, no module edit required.
Idempotent by external id
Every pulled record is keyed by its Employment Hero id and a payload hash. Running the job again updates in place and skips unchanged rows, so a repeat run never duplicates.
Day in the life
A morning sync, nothing to babysit
The scheduled job runs and pages through onboarding workflows and goals from the Employment Hero people platform. New workflows land in Odoo against the right employee, in-progress ones update their status and dates, and unchanged rows are skipped. A goal that references an employee not yet linked is left unresolved rather than crashing the run, and one malformed record is logged as an error line while the rest of the batch completes. Contractors arrive flagged on the employee form with their business number filled in. You open the run record to see counts of created, updated, skipped and failed.
Edge cases
The cases most modules quietly ignore.
In the shipped code today, each one a place where a cheaper module silently does the wrong thing.
Re-running a job finds each record by its Employment Hero external id and a hash of the mapped values, so a repeat run updates in place and reports unchanged rows as skipped instead of creating duplicates.
Each record is processed inside its own savepoint. One bad row is logged as an error line and rolled back on its own, the run continues, and it ends in a partial state rather than aborting everything.
The employee link resolves through the external id cross reference. If an onboarding row or goal points at an employee that has not been synced yet, the relation is left empty rather than failing, so you run the employee sync first and re-pull.
List endpoints are pulled page by page using the people platform page index and size parameters, stopping on a short or empty page, so a large organisation is fetched completely without one giant request.
Both shipped jobs treat the Employment Hero copy as authoritative on pull, so a value changed upstream overwrites the Odoo record on the next run while your local edits do not silently win.
Onboarding and goal records carry a company and are guarded by record rules, and external id lookups are scoped to the connection, so a multi-company database keeps each organisation's data separate.
The shared engine retries transient failures and rate-limit responses with exponential backoff and jitter, honours a server Retry-After, and refreshes the OAuth token lazily, so a brief upstream wobble does not fail the run.
What is inside
Built to do the job, end to end.
- Onboarding and goal models. eh.hr.onboarding and eh.hr.goal, each with employee, status, dates and full mail chatter for tracking, plus list, form and search views with group-by filters.
- Contractor fields on the employee. A contractor marker and a contractor business number are added to the standard employee form, shown in the HR settings area, so you filter and report on contractors without a separate model.
- Shipped endpoints, mappings and jobs. Onboarding and goal endpoints, starter field mappings and two pull sync jobs install as data. Mappings are marked so an upgrade will not overwrite your tuning.
- Scheduled and manual runs. The shared engine cron runs scheduled jobs daily, and you can trigger any job on demand. Each run records created, updated, skipped and failed counts with per-record lines.
- Security and isolation. Access is split between an Employment Hero user who reads and a manager who edits, with per-company record rules on both new models.
Honest about the edges
What this does not do, so nothing surprises you.
- Sync is one direction. Both shipped jobs pull from the Employment Hero people platform into Odoo. The module does not push Odoo changes back upstream.
- Runs are scheduled or manual pulls. This module does not register webhook subscriptions, so updates land on the next scheduled or manual run rather than the instant they happen upstream.
- The onboarding and goal records are lightweight by design. They hold the workflow name, status, dates and goal text, not the full document, form or task content held in the people platform.
- Starter field mappings assume a typical payload shape. If your organisation returns different source paths, adjust the mapping lines to match before relying on the data.
- Requires a configured Employment Hero connection from the base module, and the employee sync should run first so the employee relation resolves through the external id cross reference.
- Built and tested for Odoo 16 Community. It depends on the standard HR and mail apps and the Employment Hero base and sync modules.
employment hero odoo integration, odoo 16 hr onboarding, employee onboarding sync, employee goals odoo, contractor management odoo, abn business number employee, external id mapping sync, idempotent api sync odoo, hr platform integration, odoo community hr, people platform sync, scheduled hr sync odoo
Need this fitted to the way you work?
ERP Heritage delivers end to end Odoo work: Odoo Implementation, Customization and Development, Integration, Migration, Consultation, Support and Training. We help teams put this module into production, shape it to their process, and keep it running.
We work with businesses across Australia (Melbourne, Sydney, Brisbane, Perth, Adelaide, Canberra) and the Middle East (Dubai, Abu Dhabi, Riyadh, Jeddah, Doha, Kuwait City, Muscat). Start a conversation at erpheritage.com.au or email info@erpheritage.com.au.
Languages
Available in 19 languages
The interface ships translated out of the box. Switch language in Odoo and the fields, menus, and messages follow.
Modules teams pair with this one.
Premium ERP Heritage modules that extend the same stack, each built to the same engineering bar.
A dependency free asynchronous job queue that runs long running and fan out work out of band of the request that...
Post Irish payslips to the general ledger on the Irish chart of accounts
Interactive drag and drop Gantt planner for Odoo 16 Community project tasks with a deterministic server side sche...
Employment Hero Connector is the integration core of the ERP Heritage Employment Hero suite, providing per compan...
The United Kingdom country pack for the ERP Heritage Employment Hero integration
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 3898 |
| Technical Name |
eh_hero_onboarding |
| License | OPL-1 |
| Website | https://www.erpheritage.com.au/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module