How teams actually use Kini with Personio.
From multi-client agencies to in-house HR teams. Kini fits the way you work with Personio, not the other way around. Five scenarios where the managed integration makes the biggest difference.
Multi-client management with separate onboarding
You serve multiple end customers, all of them on Personio: each one connects through their own Magic Link onboarding. Kini keeps every client cleanly separated while you orchestrate centrally.
Applicants straight into Personio
Applications from Stepstone, Indeed, Heyflow, Perspective, Jobrapido or multiposters land directly in your customer's Personio account, with screening questions, custom fields and duplicate detection. Your team never has to download, forward or re-enter applicant data.
Custom field mapping without engineering
Kini normalises enums, locations, sources and custom fields between Personio and external systems, even when attributes do not map 1:1. If a value is missing, Kini's fallback logic (pre-set default values) fills the gap before the record lands in Personio.
Screening questions and consent flow
Candidates answer Personio's dynamic and predefined screening questions right where they apply, and every answer lands structured inside the candidate record, with the consent flag already set.
Source attribution via API
Kini hands the application source over to Personio via API identification, not via UTM parameters, which often get lost on the application submit step. That makes it clearly traceable which channel produced which application.
Every field. Every entity.Exactly where it belongs.
Kini syncs the full Personio data model. Jobs, candidates, applications and custom fields. Bi-directionally across every connected channel. No intermediate storage, no manual exports, no data sitting in between.
Jobs
Candidates + Applications
Custom Fields
How candidates and applications relate differs per ATS. In Personio, an application submit creates a single linked record, which is why we treat both entities together here.
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.
From Personio API to production go-live in minutes.
Kini connects to Personio via API or magic link. Fields are mapped automatically, the connection is tested and your integration is live.
Step 1Connect
Your customer receives a Magic Link from Kini and grants access to their Personio account. No passwords shared, only encrypted API tokens stored.
Step 2Map
Kini automatically maps fields, enums, locations and screening questions between Personio and your connected channels. No manual configuration needed.
Step 3Test
Run a test job and a test candidate through the full flow. Kini checks field mapping, edge cases and consent flags before anything goes live.
Step 4Go-live!
Real traffic, real applications, routed directly into Personio in real time. Monitoring and alerts from day one.
with your stack?
What makes Kini different for Personio customers.
Other tools connect. Kini manages. Here is what that means in practice. For GDPR, field mapping, job board compatibility and everything that breaks when nobody is watching.
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 Personio integration.
Everything about how Kini connects to Personio. From setup and data sync to GDPR compliance and DACH job board compatibility.
Kini syncs three objects with Personio: jobs are read from Personio, and candidates and their applications are written into it. Custom fields, enums, locations and screening questions are mapped alongside them, so records arrive complete instead of needing manual clean-up afterwards.
No. Personio stays your system of record. Kini is the connectivity layer around it: jobs, candidates and applications are synced between Personio and your connected recruiting channels. You extend what Personio already does, without replacing it and without a second system to maintain.
No. The Personio integration is pre-built, so there is no development project on your side. You send your customer a Magic Link, they connect their own Personio account, and Kini auto-detects and pre-maps fields, enums, locations and screening questions. Kini then operates and monitors the connection as a managed service.
There is no development project on your side. Your customer connects their Personio account through a Magic Link, Kini pre-maps the fields automatically, and a test job and test candidate run through the full flow before anything goes live. The work is configuration and verification, not engineering.
By default, Kini checks Personio for new and changed jobs once an hour. The interval is set per company and can be shortened on request. Applications from your connected channels are sent to Personio as they come in.
Yes. StepStone, Indeed and regional boards each have their own required fields, screening patterns and encoding rules. Through Kini Shop, jobs from Personio are published with those requirements handled.
Kini operates the connection as a managed service: syncs are monitored and failed syncs are retried automatically. If Personio changes its API or a mapping breaks, the Kini team updates the connector, and every application keeps a visible sync status in the meantime.
It is built for GDPR-compliant use. Data that passes between Personio and your connected channels is processed by Kini in Frankfurt, Germany, under a data processing agreement (DPA). Kini deletes or anonymizes personal applicant data 180 days after an application is created.
You can, but then you build and maintain it yourself: the initial connection, the field mapping, and every change Personio makes to its API afterwards. Kini's Personio integration is pre-built and operated as a managed service: your customer connects via Magic Link, and the Kini team handles mapping and maintenance.
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."
