Employment Hero Onboarding
Pull onboarding workflows, employee goals and contractor details from the Employment Hero platform into Odoo, on a schedule, with no code.
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
Models Community does not ship
Odoo Community has no onboarding or goal record. This module adds eh.hr.onboarding and eh.hr.goal, both with chatter, list, form and search views, so platform workflows and objectives have a home in Odoo.
Keyed to your employees
Every imported record resolves to the Odoo employee through an external id cross reference and is keyed by its source id. Re-running a job updates in place and an unchanged payload is a no-op, so repeat runs never pile up duplicates.
Mappings you can edit
Endpoints, field mappings and sync jobs ship as data. Adjust source paths to match your organisation payload, change which fields land where, and preview a run as a dry run, all from the user interface.
Day in the life
What a sync run looks like
On schedule or on demand, the onboarding and goals jobs page through the Employment Hero platform, map each record to its Odoo fields, and match it to an employee by external id. New workflows and goals are created, changed ones are updated in place, and unchanged ones are skipped. Each record is wrapped in its own savepoint, so a single malformed entry is logged as an error line and the run carries on, ending in a partial state you can review rather than failing the whole batch. Contractor markers added by this module appear on the employee form, ready to filter and report on.
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.
Records are keyed by their external id through the cross reference, so re-running a job never duplicates and an unchanged payload (same hash) is skipped as a no-op.
Each record runs inside its own savepoint. A failed write rolls back just that record, is recorded as an error line, and the run continues, ending in a partial state instead of aborting everything.
The shared client retries transient failures, timeouts and rate-limited (429) responses with exponential backoff plus jitter, honouring a server Retry-After up to a safe clamp, and raises immediately on non-retryable errors.
Onboarding and goals are pulled page by page at a configurable page size, reading items from the declared items path, so large datasets sync without loading everything in one call.
The change hash folds in a fingerprint of the mapping itself, so editing a mapping line or transformer forces existing records to be rewritten on the next run instead of being skipped as unchanged.
Onboarding and goal records carry a company and a global record rule isolates them per company, with company-less records visible to all.
The platform connection uses OAuth2 Bearer auth with lazy refresh, so an expiring access token is renewed from the stored refresh token without manual intervention.
What is inside
Built to do the job, end to end.
- Two new HR records. eh.hr.onboarding holds the workflow name, status, start and completion dates and the linked employee. eh.hr.goal holds the title, description, status and due date. Both inherit mail.thread and mail.activity.mixin for chatter and activities, and ship with list, form and search views, group-by filters and dedicated menus.
- Contractor fields on the employee. The standard employee gains a contractor marker and a contractor business number field (for example an ABN), shown on the employee form and hidden until the contractor flag is set. The fields are added and surfaced here; they are populated by the employee sync in the related HR module.
- Editable sync configuration. Two pull mappings with their mapping lines, two list endpoints and two scheduled pull jobs ship as data. Mappings are marked non-updating so your tuning survives upgrades. Transformers handle external-id employee matching and date parsing out of the box.
- Built on the suite engine. Sync is driven by the shared orchestrator and HTTP client: idempotent pulls, per-record savepoint isolation, retry and rate-limit handling, conflict policy, delta cursor support and dry-run preview. Access is governed by suite user and manager groups with read-only users and full-control managers.
Honest about the edges
What this does not do, so nothing surprises you.
- Sync is one way for this module: onboarding workflows and employee goals are pulled from the Employment Hero platform into Odoo. There is no push of these records back to the platform.
- This module does not ship webhook wiring for its jobs. Onboarding and goals sync on a schedule or on demand, not by real-time webhook. Real-time delivery requires the separate suite webhook module and per-job detail endpoints, which are not configured here.
- The contractor marker and business number fields are added to the employee and shown on the form, but this module ships no job that fills them. They are populated by the employee sync in the related HR module.
- Policies and forms endpoints are present in the catalogue as read scaffolding only. No mappings or jobs are shipped for them, so they are not synced by this module.
- Requires the suite sync engine module and a configured Employment Hero connection. Field mappings ship as starters and must be adjusted to match your organisation payload shape.
- Built and tested for Odoo 18 Community. No Enterprise dependency.
employment hero onboarding odoo, employment hero integration odoo 18, hr onboarding sync odoo community, employee goals odoo, contractor abn odoo employee, odoo 18 hr connector, scheduled hr data sync, external id employee matching, field mapping no code odoo, one way hr import 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 18 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 | 3929 |
| 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