Create the onboarding of a joiner from an HR system event
Start the onboarding of a joiner who is not an employee in Primo yet, from what an HR system or an automation knows: first name, last name, work email, the start date, and a free data object with everything else. Primo starts the whole flow, the way an admin does from the cockpit short form: the onboarding ticket and its steps, or the Onboarding Agent when it runs the onboardings of the company. data is kept on the onboarding as the hire text the agent reads. Refused with 409 DUPLICATE_ONBOARDING when an open onboarding already has this email, or the same name and start date, so a repeated call creates nothing; 502 FAIL_TO_CREATE_ONBOARDING_TICKET and 503 ONBOARDING_AGENT_STATUS_UNAVAILABLE created nothing, call again. For an employee who already exists in Primo, use createOnboarding with their id instead.
Authorizations
Use your Primo API key in the Authorization header as Bearer <API_KEY>.
Body
First name of the joiner
1Last name of the joiner
1Work email of the joiner
^(?!\.)(?!.*\.\.)([A-Za-z0-9_'+\-\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\-]*\.)+[A-Za-z]{2,}$First day of the joiner (YYYY-MM-DD or ISO 8601). Required by the classic onboarding, read by the agent.
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$Everything else the caller knows about the joiner, as a free JSON object (job title, team, manager, location, contract…), at most 20000 characters once serialized. Kept on the onboarding and read by the Onboarding Agent. May hold personal data.
Response
PENDING, SCHEDULED, IN_PROGRESS, CLOSED, CANCELED COCKPIT, MERGE, KOMBO, API ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$HR records from the connected HRIS (Kombo) for this onboarding
Every email address of the employee being onboarded. Empty while the onboarding has no employee.
How the onboarding holds its steps: ACTIONS (the onboarding steps and their plain tasks) or INTENTS (typed tasks under its ticket, run through the intent tools such as executeEmployeeCreationIntent). Null while it has neither a ticket nor a step, and for an onboarding run by the agent.
ACTIONS, INTENTS How many of its steps are through, out of how many: on ACTIONS its steps done, scheduled or skipped; otherwise the typed tasks of its ticket completed or cancelled. Null while it has no step.
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$The hire an admin added by hand in the cockpit short form, before they are an employee in Primo