What Kini handles for employers on Workable.
Workable keeps jobs, their questions and the candidates on each job. Kini reads the first two and creates candidates for every end customer you connect, so applicants from your channels appear in Workable like any other applicant.
Published jobs with location and salary range
Workable jobs move between draft, published, closed and archived. Kini takes the published ones with title, department, workplace type, location down to city and zip code, and the salary range with its currency, so your channels show the details candidates check before they decide to apply.
Applicants created as applied, not uploaded
Workable tells candidates who applied apart from candidates a recruiter uploaded. Kini creates every applicant as applied, so they appear in the job's pipeline like anyone who used the employer's careers page and receive Workable's usual thank-you email for their application.
The job's questions inside your application form
Kini reads the questions defined on each Workable job, including which ones are required, and shows them in your application flow. The answers travel back with the candidate, each tied to its question, so recruiters read them in Workable right next to the resume.
Resume and profile in a single record
When Kini creates the candidate, it sends the resume together with name, email, phone, address, cover letter and social profiles. Workable accepts resumes as PDF, DOC, DOCX or RTF, so the candidate record is complete from the moment it shows up on the job.
Access limited by the token's scopes
The employer generates a Workable API token with only the scopes this connection needs: reading jobs and writing candidates. Workable checks every request against those scopes, so employee records, offers and other parts of the account stay closed to the connection.
Every field. Every entity.Exactly where it belongs.
Kini works with three Workable records: jobs and their questions come in, candidates go back on the job they applied to. Field names match Workable's API reference.
Jobs
Job Questions
Candidates
Workable addresses each job by its shortcode, a code the system generates, rather than by its internal identifier. Kini keeps the shortcode with every imported job, because a new candidate is created on a job through exactly that code.
Operations like GET, POST, PATCH are documented per endpoint in the . The primary source for field definitions. Kini adds mapping and fallback logic on top.
End-to-end GDPR consent
Every application that flows through Kini carries a consent flag, mirrored on the target system's side and traceable in audits.
Native-language custom fields
Locations, departments and sources are mapped correctly even when they use German naming conventions or regional variants, whether your customers sit in DACH or operate internationally.
Application flows for a wide range of job boards
Stepstone, Indeed, Jobrapido and regional boards each have their own required fields, screening patterns and encoding rules. Kini's mapping engine is trained for those: out of the box, not as a custom project.
Operated by the Kini team
Kini runs the connection for you, including monitoring and alerts. If a vendor changes an API or a mapping breaks, our team fixes it before it reaches your funnel. Operated from Germany.
Frequently asked questions about the Workable integration.
Which Workable jobs Kini publishes, how applicants are created on them, and what an employer generates in Workable before the connection starts.
Published jobs and their questions come in from Workable. Kini creates candidates on those jobs, with resume, contact details, cover letter, answers and the channel as source. Kini does not change jobs in Workable and does not read employee data, offers or requisitions.
Jobs in the state published. Workable uses the state closed for jobs that are handled internally or confidentially, and those stay out, as do drafts and archived jobs. When a published job changes state in Workable, Kini archives it at the next import and your platform is informed through Kini's job updates.
A Workable API token. An account admin generates it in Workable's integration settings and selects the scopes for reading jobs and writing candidates. Workable shows the token only once, so the admin enters it in Kini's setup right after generating it.
Yes, because they are created as applied. Workable's documentation states that a candidate created through the API as applied receives the thank-you-for-applying email, while an uploaded candidate does not. Candidates from your channels therefore get the same confirmation as applicants on the employer's own careers page.
No. Workable stays the employer's system of record for jobs, candidates and the hiring process. Kini links the published jobs with the channels where candidates find them and creates the resulting applicants in Workable, where the hiring team keeps working as before.
Through the sync status that Kini records for every application. Your platform receives each change by webhook or reads it from Kini's API, and a rejection the target system expects, such as a job that is no longer published, is marked as an expected failure rather than an error.
Kini processes applications in Frankfurt within the EU and provides a data processing agreement. After 180 days, Kini anonymises an application and drops its contact details, attachments, notes and screening answers. The candidate created in Workable is then governed by the employer's settings there.
Trusted by recruiting teamsacross europe.
From enterprise HR platforms to lean recruiting boutiques. Teams use Kini to connect their tools without involving engineering. Here's what they say.
"Kini syncs candidates from Perspective straight into our customers' ATS. That saves us manual transfers and around four hours a week."
"Kini gets enterprise customers on SAP SuccessFactors live much faster. Fewer technical hurdles in sales, around 20% more conversion."
"With Kini, we sync candidates straight into our customers' ATS through 65+ integrations. We don't need an extra full-time hire for it."
