Recruitment to HR
Workable to Sympa integration: hire as a data card on a dedicated Sympa interface
With an integration between Workable and Sympa, a candidate in the Workable Hired stage becomes a new employee card in Sympa, with name, email, phone, job title, organisational unit and start date. A ready-made Workable connector is not among Sympa's offerings, so KoppelHet writes through the Sympa Integration API to an interface your administrator sets up for this integration.
What the integration does
Organisations that recruit in Workable and use Sympa as their HR system find no Workable connector at Sympa. They enter every hire in Sympa by hand, and HR has to translate the department from Workable to the organisational units that exist in Sympa every time.
- The recruiter moves the candidate to the Hired stage in Workable.
- KoppelHet fetches candidate, job and offer and checks that the offer has been accepted.
- Department and job title are translated to the option values of the Sympa interface.
- KoppelHet creates the employee card and records the card's identifier with the candidate.
- HR adds contract and salary in Sympa.
What to watch for with Workable and Sympa
- Sympa's connector page only lists Teamtailor for recruitment, not Workable. Sympa says an own team can build an integration on the Sympa API; KoppelHet does that for Workable with the Integration API.
- A Sympa interface has no fixed fields; the administrator chooses which fields are on it and whether POST and PATCH are allowed. We agree an interface with the administrator with exactly the fields that come from Workable, so no other HR data is exposed.
- In Workable the start date is a variable in the offer document, stored as text. Sympa only accepts a date as yyyy-MM-dd without time. KoppelHet converts the text and stops with an alert if the date cannot be read, instead of sending an empty start date.
- Option fields in Sympa, such as organisational unit or job title, must exactly match a value in the interface mapping table. Departments in Workable can be named freely, so we record the Sympa value per Workable department; a new department first produces an alert.
- A new card can usually be retrieved in Sympa within a minute, but it can take up to thirty minutes. Workable may report a stage change again. KoppelHet therefore keeps track itself of which candidate already has a card and uses the Workable candidate number as unique identifier.
- Table rows that come in through the API are approved in Sympa straight away. The salary from the Workable offer would then be in Sympa without a check; in the first version KoppelHet only sends the card, and HR records contract and salary.
- The Sympa API cannot delete anything. If a candidate is disqualified in Workable after Hired, KoppelHet prepares a task for HR to deal with the card in Sympa.
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
Does Sympa have an integration with Workable?
We did not find one in Sympa's public list. Check with Sympa to be sure; otherwise KoppelHet builds on the API.
Who sets up the interface in Sympa?
Your Sympa administrator, under Settings, API. KoppelHet provides the list of fields and option values.
Do changes to the offer after the hire come along?
Not in the first version. Updating a changed start date through PATCH can be added later as an extension.
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 and GET /candidates/:id, /jobs/:shortcode and /candidates/:id/offer (state; document_variables with value/body as text). Token with r_candidates and r_jobs.
- To Sympa through the Integration API (OData 4.0) - POST api/{interface} with @odata.type and the unique identifier; response 204 with Location header. API key in the X-ApiKey header or basic authentication. Dates yyyy-MM-dd, numbers with a period, option values from the mapping table, no DELETE.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Workable | Field in Sympa | Notes |
|---|---|---|
firstname en lastname | Voornaam en achternaam (interfaceveld) | |
email | Privé-e-mail (interfaceveld) | |
phone | Telefoon (interfaceveld) | |
document_variables start_date (aanbod) | Startdatum | As yyyy-MM-dd, without time |
department (vacature) | Organisatie-eenheid | Value from the interface mapping table |
title (vacature) | Functie | Value from the interface mapping table |
Workable-kandidaat-ID | Uniek kenmerk van de kaart |
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