Workable logoWorkday logo

Recruitment to HR

Workable to Workday integration: hired candidates as pre-hire and hire in Workday

With an integration between Workable and Workday, a candidate who reaches the hired stage in Workable automatically becomes a pre-hire in Workday, and KoppelHet starts the hire on the position linked to the job, with start date and job from the accepted offer. A freelancer from Workable becomes a contingent worker in Workday instead of an employee.

What the integration does

Organisations that recruit in Workable and manage workers in Workday retype every hire. After a signed offer HR creates the pre-hire by hand and looks up the position. Freelancers regularly end up in Workday as employees, and accounts are not ready on day one because the hire was started late.

  1. The recruiter moves the candidate in Workable to the hired stage.
  2. KoppelHet fetches candidate, job and offer and checks that the offer has been accepted.
  3. A pre-hire is created in Workday with name, contact details and the Workable candidate number as reference.
  4. For a permanent or temporary employee KoppelHet starts the hire on the position from the job code; for a freelancer a contract as contingent worker.
  5. Workday runs the approvals you have configured. An error, such as a filled position, appears in the KoppelHet platform.
Workable → KoppelHet → WorkdaySOURCEWorkableTARGETWorkdayKoppelHetmapping · logging · monitoringWorkable → KoppelHet → WorkdaySOURCEWorkableTARGETWorkdayKoppelHetmapping · logging · monitoring
Out: Candidate with name, email, phone and address · Accepted offer with start date and salary · Job with internal code and employment type · Pre-hire in Workday · Hire or contract as contingent worker

What to watch for with Workable and Workday

  • A job in Workable has a free field for an internal code. We have recruiters enter the Workday position ID there when opening the job. That way KoppelHet knows for every hire on which position the hire must start, without a separate lookup table someone has to maintain.
  • Workday has two kinds of workers, each with its own process. An employee comes in through Hire Employee, a freelancer or temp through a contract as contingent worker. KoppelHet chooses the process based on the employment type of the Workable job.
  • Workable only fills in the hire date at the moment the candidate reaches the hired stage. KoppelHet does not use that date as start date in Workday; the start date comes from the accepted offer, so a hire in November starting in January also takes effect in January.
  • Workday now calls a hired candidate a pre-hire, but the web service to create one is still called Put_Applicant, so existing integrations keep working. KoppelHet first creates the pre-hire and only then starts the hire, so a rejected hire can be retried without a second person.
  • Workable can disqualify a candidate or mark them as withdrawn after they were hired. KoppelHet checks that in the daily round and reports it to HR. Rescinding a hire remains a separate process with its own approval in Workday.
  • If the organisation recruits in Workable for several countries, the job location determines the country in Workday. Required data such as the national ID number differs per country; HR completes it in Workday and it does not come from the recruitment system.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Do recruiters need to do anything differently?

They enter the Workday position ID as the internal code for a new job, and make sure the offer has a start date. If either is missing, they get a notice before anything happens in Workday.

Are approvals in Workday skipped?

No. KoppelHet starts the hire or the contract; the approvals you configured still apply.

Technical details for IT

For those who want to know how it works under the hood: APIs, fields and sources used.

  • Workable through a subscription on candidate_moved with stage_slug hired, signed with X-Workable-Signature. Then GET /candidates/:id (hired_at, disqualified, withdrew), /jobs/:shortcode (code, employment_type, location) and /candidates/:id/offer (state accepted, document_variables, salary). Token with read scopes only.
  • Workday through the Staffing web service with an Integration System User. Put_Applicant for the pre-hire (Workable ID in External_Integration_ID_Data), then Hire_Employee (Hire Employee business process with Position_Reference, Hire_Date and Location_Reference) or Contract_Contingent_Worker for freelancers.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in WorkableField in WorkdayNotes
id (kandidaat)External_Integration_ID_DataRecognises a second notification for the same candidate
firstname en lastnameLegal_Name_Data (First_Name, Last_Name)Name prefixes according to the country's name format
email en phoneEmail_Address_Data en Phone_Data (privé)
code (vacature)Position_ReferenceRecruiters enter the Workday position ID as internal job code
employment_type (vacature)Hire_Employee of Contract_Contingent_WorkerThrough a table per employment type
Startdatum (document variable van het aanbod)Hire_Date of Contract_Start_Date
location (vacature)Location_ReferenceThrough a lookup table
Salaris (amount, frequency, currency_iso)Compensation (subproces)Only if HR wants it; otherwise HR enters it in Workday

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.