Recruitment to HR
Recruitee to Zoho People integration: hired candidates in the Zoho People employee form
With an integration between Recruitee and Zoho People, a candidate hired in Recruitee automatically becomes a record in the Zoho People employee form, with employee ID, name, work email, start date, department and job title. Whether the new colleague gets an invitation straight away or only a profile first is agreed per organisation.
What the integration does
Organisations that have Zoho People as HR system and recruit in Recruitee instead of Zoho Recruit retype the details of new employees. Employee IDs are then handed out by hand, and a duplicate number or a typo in the email address later blocks the login.
- The recruiter marks the candidate as hired in Recruitee and fills the profile fields with work email and start date.
- KoppelHet determines the next employee ID according to the agreed range and checks that it is still free.
- KoppelHet adds a record to the Zoho People employee form.
- Zoho People sends an invitation, or prepares the person as a profile without login, depending on the agreement.
- If Zoho People returns an error, HR sees the error code and the field in the KoppelHet platform.
What to watch for with Recruitee and Zoho People
- Zoho People wants an employee ID, first name, last name and email address for every new employee. Recruitee has no employee ID, so KoppelHet assigns one from the range HR uses and first checks whether the number already exists.
- Without an extra setting Zoho People creates the employee as inactive and sends an invitation. With isNonUser the person is added only as a profile, without login; that suits a start date that is still far away.
- Making someone active immediately is only possible if a password is supplied on creation. KoppelHet does not do that, so the new colleague chooses a password through the invitation.
- The right to add records belongs to the ZOHOPEOPLE.forms.CREATE scope, and Zoho names it only for standalone Zoho People subscriptions. If the organisation runs Zoho People inside Zoho One or People Plus, KoppelHet first checks whether the integration may add records.
- Fields such as department and manager are references to other records in Zoho People. KoppelHet looks up the right record for the department from Recruitee before creating the employee.
- Zoho People runs in its own data centre, for example zoho.eu for European customers. KoppelHet uses the domain and OAuth client of the data centre the organisation is in.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Why not Zoho Recruit?
Zoho Recruit connects to Zoho People out of the box. If you keep Recruitee as ATS, you do not have that connection and need this integration.
Who chooses the employee ID?
HR. We agree the range or prefix at the start, and KoppelHet follows it.
Do custom fields from Recruitee come along too?
Yes, if they exist in the Zoho People employee form. We map them on the field's label name.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Recruitee reports the hire through the candidate_moved webhook with the hire stage category, signed with X-Recruitee-Signature; offer and profile fields through the ATS API.
- To Zoho People through POST /people/api/forms/json/employee/insertRecord with header Authorization Zoho-oauthtoken and scope ZOHOPEOPLE.forms.CREATE. inputData as JSON with required EmployeeID, FirstName, LastName and EmailID; optionally isNonUser, or isDirectAdd with password. Response with the pkId of the new record. Threshold of three hundred requests per minute, then a five-minute wait.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Recruitee | Field in Zoho People | Notes |
|---|---|---|
id van de kandidaat of reeks van HR | EmployeeID | Required in Zoho People |
name | FirstName en LastName | Recruitee name split |
Zakelijk e-mailadres (profielveld) | EmailID | Becomes the login address |
Startdatum (profielveld) | Dateofjoining | |
offer.department | Department | As a reference to an existing record |
Vacaturetitel of functie (profielveld) | Designation | |
E-mail leidinggevende (profielveld) | Reporting_To | Looked up in Zoho People |
phones[0] | Mobile |
Related
Recruitee → ADP Workforce Now
Recruitee to ADP Workforce Now integration: hired candidates as an in-progress hire
Recruitee → AFAS Profit
Recruitee to AFAS integration: from hired candidate to new employee
Recruitee → AlexisHR
Recruitee to AlexisHR integration: hired candidates as employees in Simployer One
Recruitee → BambooHR
Recruitee to BambooHR integration: hired candidates in BambooHR without clicking and retyping