Employment Hero Onboarding Sync
Pull onboarding workflows, employee goals and contractor details out of the Employment Hero people platform and into Odoo, on a sync engine 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
Onboarding and goals in Odoo
Community has no onboarding or goal model. This ships both as tracked records, linked to the employee, so people ops stop chasing status in spreadsheets and read it where the rest of HR lives.
Tune the mapping, not the code
Endpoints, field mappings and sync jobs ship as data. When your Employment Hero payload differs, change the source path and target field from the screen. The starter mappings carry noupdate so an upgrade never overwrites your edits.
Safe to re run, every time
Each record is keyed by its external id, so a second run updates in place rather than duplicating. A failed record rolls back alone in a savepoint, transient API errors retry with backoff, and every run writes an audited line per record.
Day in the life
A new starter and a quarterly goal land in Odoo
The onboarding pull job runs after the employee job, so the external id cross reference already resolves the person. A new starter workflow arrives as an eh.hr.onboarding record with its status and start date, linked to the right employee. Their first quarterly objective arrives as an eh.hr.goal with a due date. A contractor hired the same week shows the contractor marker and business number on the standard employee form. People ops open the HR Workflows menu and see onboarding and goals grouped by employee and by status, no spreadsheet involved. When a workflow completes upstream, the next run updates the same record in place rather than creating a duplicate.
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.
Every record is keyed by its external id through eh.external.id, so re running a job updates the existing onboarding or goal in place instead of creating a second copy.
Each record is processed inside its own database savepoint. One bad row, for example a missing required title, rolls back alone and is logged as an error line while every other record in the batch still commits.
Transient API failures and 429 responses retry with exponential backoff and jitter, honouring a server Retry-After header up to a safe clamp, instead of failing the whole run on a blip.
List endpoints are pulled page by page at a fixed page size with a hard page cap, so a large onboarding or goal set is fetched completely without an unbounded loop.
The employee link resolves through the external id cross reference, not a name guess, so it holds when ids differ. A record whose employee cannot be resolved is logged rather than attached to the wrong person.
Onboarding and goal records carry a company and an isolation rule, so each company sees only its own, while records left without a company stay visible to all.
When a job runs in delta mode the cursor only advances past records that processed cleanly, so a failed or concurrently changed record is re fetched next run instead of being skipped forever.
What is inside
Built to do the job, end to end.
- Two synced models. eh.hr.onboarding carries name, status, start and completion dates. eh.hr.goal carries title, description, status and due date. Both inherit chatter and activities, are ordered by employee and link back through the external id cross reference.
- Contractor flags on the employee. The standard hr.employee form gains an Is Contractor marker and a Contractor Business Number field, shown only when the contractor box is ticked, so contractors are filterable and reportable without a separate model.
- Endpoints, mappings and jobs as data. Ready made REST endpoints for onboarding and goals, two pull mappings with per field source paths and transformers, and two sync jobs with conflict policy and external id path, all shipped as records you can edit from the screen.
- Built on the shared sync engine. Field level mapping with transformers, external id keyed upserts, per record savepoint isolation, retry with backoff, paginated fetch and a delta cursor all come from the Employment Hero sync engine this module depends on.
- Audited runs. Every sync run records a line per record with its outcome, created, updated, skipped or error, so a deployment can see exactly what each pull did.
Honest about the edges
What this does not do, so nothing surprises you.
- Sync is one way. Both shipped mappings pull from Employment Hero into Odoo. The module does not push onboarding or goal changes back, and there is no two way sync or conflict resolution screen.
- Updates run on the scheduled pull job, not in real time by default. Near instant single record updates on an upstream change require the separate webhook companion module from this suite, which this module does not include.
- An Employment Hero account with API access for the people platform is required. This module reads through the shared engine and does not provision or replace that account.
- The shipped mappings are starters. Source paths assume a representative payload shape and may need adjusting from the screen to match your organisation's exact field names.
- Onboarding and goals are tracked as lightweight records for visibility and reporting. This is not a workflow builder and does not drive checklist steps or send onboarding tasks back to Employment Hero.
- The contractor marker and business number are surfaced on the employee and populated by the employee sync from the platform. This module adds the fields and the view, not a separate contractor mapping.
Employment Hero Odoo integration, Employment Hero onboarding sync, Odoo 17 HR sync, employee goals Odoo, contractor tracking Odoo, Employment Hero API connector, Odoo onboarding module, HR data sync Odoo Community, no code field mapping Odoo, Employment Hero employee sync
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 17 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 | 3949 |
| 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