Recruitment to HR
Workable to SAP SuccessFactors integration: hire as person, employment and job in Employee Central
With an integration between Workable and SAP SuccessFactors, a candidate in Workable's Hired stage becomes a new employee in Employee Central, with person, employment and job, on the start date from the offer and with the right legal entity, department and job. We could not find a SuccessFactors integration of Workable's own; KoppelHet builds on the APIs of both systems.
What the integration does
Organisations that recruit locally in Workable and use SAP SuccessFactors Employee Central globally send hires by email or form to an HR service centre. The new employee is retyped there, with the risk of a wrong legal entity or department code and a second person for someone who worked there before.
- The recruiter moves the candidate to the Hired stage in Workable.
- KoppelHet retrieves candidate, job and offer and checks that the offer was accepted.
- KoppelHet checks in Employee Central whether the person already exists; if so, HR decides on a rehire.
- KoppelHet creates person, employment and job, with a hire event on the start date.
- If a step fails, for example because of an unknown department code, KoppelHet repeats only that step after correction.
What to watch for with Workable and SAP SuccessFactors
- Employee Central expects a new employee in a fixed order, first the person, then the employment and then the job with a hire event. KoppelHet remembers per Workable candidate which step succeeded, so an error halfway does not produce a second person.
- Workable fills a hired date at the moment the candidate moves to Hired. Employee Central works with the effective date of the employment. KoppelHet takes the start date from the accepted offer, not the hired date, so the job in Employee Central starts on the first working day.
- Workable has legal entities per account, Employee Central has legal entities as foundation objects with their own code. Per Workable entity we record the code in Employee Central; a job without an entity does not go through.
- Department and job title are free text on the job in Workable, and foundation object codes in Employee Central. KoppelHet translates through a table and stops on an unknown value, instead of putting text into a code field that Employee Central rejects.
- Employee Central has its own rehire and records at termination whether someone may return. Workable does not know that a candidate worked there before. KoppelHet therefore first searches Employee Central by email and name and passes a match to HR.
- The salary in Workable has an amount, interval and currency, while compensation in Employee Central depends on pay components per country. KoppelHet does not carry the salary in the first version; HR records it in Employee Central, and carrying it over can be added later.
- SAP is ending basic authentication for the SuccessFactors APIs. KoppelHet uses OAuth 2.0 with its own API user from the start, so the integration does not need to be set up again at that change.
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 Workable when SuccessFactors also has a recruiting module?
That is the organisation's choice, often per country or division. The integration lets Workable remain the recruiting system and Employee Central the source for employees.
Do BSN and bank account come from Workable?
No. HR or the employee enters them in Employee Central, or Dutch payroll does.
We already have an integration platform. Does this fit alongside it?
Yes. The integration runs on the KoppelHet platform and asks nothing of your existing platform. Every action is in the audit logging.
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 (X-Workable-Signature, HMAC-SHA256). Then GET /candidates/:id, /jobs/:shortcode (department, location), /legal_entities and /candidates/:id/offer (state accepted; document_variables with start_date). Token with read scopes only.
- SAP SuccessFactors Employee Central through OData v2 upserts in the order PerPerson and PerPersonal, EmpEmployment and EmpJob with a hire event; PerEmail and PerPhone for contact details; personIdExternal as key. Department, legal entity and job classification are foundation objects; okToRehire sits on EmpEmploymentTermination. OAuth 2.0 with SAML assertion; basic authentication is being phased out.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Workable | Field in SAP SuccessFactors | Notes |
|---|---|---|
Kandidaat-ID | Referentie bij de nieuwe medewerker | Prevents duplicate creation |
firstname en lastname | PerPersonal (firstName, lastName) | |
email | PerEmail (privé) | |
phone | PerPhone | |
Juridische entiteit van de vacature | EmpJob.company | Through a table to the legal entity in Employee Central |
department van de vacature | EmpJob.department | Foundation object code |
title van de vacature | EmpJob.jobCode | Through a table to the job classification |
Locatie van de vacature | EmpJob.location | |
Document variable start_date uit het aanbod | EmpEmployment.startDate |
Related
Workable → ADP Workforce Now
Workable to ADP Workforce Now integration: from the Hired stage to an in-progress hire per ADP company
Workable → AFAS Profit
Workable to AFAS integration: a candidate in the hired stage starts onboarding in AFAS
Workable → BambooHR
Workable to BambooHR integration: hire with salary interval and later changes
Workable → Dayforce
Workable to Dayforce integration: hire from the Hired stage, validated first