Automate onboarding
Create employees and push hires into downstream systems.

Build in-app HR automations that read and write Personio employee, recruiting and document records, trigger workflows from Personio webhooks and deliver self-serve integrations to customers.
Create employees and push hires into downstream systems.
Post applications and documents from career pages automatically.
Use Personio webhooks to trigger tenant-specific workflows.
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Integrate and automate employee lifecycle, recruiting applications, documents, time-offs and HR reports in Personio. The connector supports API operations to list and manage employees, create recruiting applications and upload documents, plus webhooks for person and application events. (developer.personio.de)
PRODUCT USE CASES
Create automated onboarding, applicant capture and HR syncs for many customer accounts. Use Personio webhooks to trigger downstream processes and publish prebuilt workflows in an embedded marketplace for customers.
Create and update Personio employee records on hire, update HR systems and revoke access on termination using company/employees endpoints. (developer.personio.de)
POST recruiting applications and upload applicant documents into Personio so candidates land in recruiting pipeline. (developer.personio.de)
Subscribe to Personio webhooks (person.created, application.updated) to start tenant-specific onboarding or notifications. (developer.personio.de)
ORCHESTRATION
Cyclr sits between your SaaS product and PersonioHR to handle authentication, govern access and orchestrate every API call per customer, at scale.
Your app requests an action for a specific customer.
Cyclr authenticates, applies policies and routes the request.
PersonioHR processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Explore PersonioHR methods you can orchestrate through Cyclr.
Gets a list of employees since last run.
Gets an employee by ID.
Gets a list of employees.
Gets a list of employees created since last run.
Create an employee.
Gets a list of employees whose birthday is the current date, or between two provided dates.
Get a list of available absence types.
Get a list of company employee absences.
Create an absence for company employee.
Create attendances for company employees.
Get a list of company employee attendances.
Update an attendance period.
Delete attendance data.
TECHNICAL DETAILS
Review the sourced authentication and API behaviour used when configuring customer-facing PersonioHR integrations in Cyclr.
https://api.personio.deClient ID and Client Secret; Company ID (X-Company-ID); optional X-Personio-App-ID and X-Personio-Partner-ID. (developer.personio.de)
Personnel; Recruiting; Documents; Time-off; Reports; Webhooks; Auth
Pagination varies by endpoint: many v1 endpoints use limit/offset; some v2 endpoints use cursor pagination. Confirm pagination per endpoint. (developer.personio.de)
Personio enforces rate limits: auth ~60/min; some endpoints (GET employees) 300/min; global v1 limits noted (2000/min); 429 returned on exceed. (developer.personio.de)
IMPLEMENTATION
Personio uses OAuth 2.0 client credentials to obtain bearer tokens; Cyclr Console must be configured to store client ID and secret securely. Confirm enabled option in Cyclr Console. (developer.personio.de)
Client ID and Client Secret; Company ID (X-Company-ID); optional X-Personio-App-ID and X-Personio-Partner-ID. (developer.personio.de)
Requires Personio API credentials and company ID; admin permissions needed to create credentials.
COMMON QUESTIONS
It automates employee lifecycle, recruiting applications, document uploads, time-off and HR reports by calling Personio Personnel and Recruiting APIs and handling webhook events. (developer.personio.de)
It uses OAuth 2.0 client credentials: Cyclr stores Client ID and Client Secret and exchanges them for a bearer token via Personio’s auth token endpoint. Tokens are short‑lived; auth endpoint rate limits apply. (developer.personio.de)
Yes. Cyclr can store per-tenant Personio credentials (client id/secret and company id) so each customer account uses its own API credential when running workflows. (developer.personio.de)
Yes. Cyclr orchestration can expose specific Personio API actions as governed MCP tools with role-based controls and reusable flows for product teams. Confirm which Personio methods you want to publish.
KEEP EXPLORING
Related HR/payroll connector for customer-facing integration workflows.
Related connectorRelated HR/payroll connector for customer-facing integration workflows.
Related connectorRelated HR/payroll connector for customer-facing integration workflows.