How to use a Righthand with Personio

Quick answer

Use a permitted Personio employee extract to prepare an attribute completeness review for HR. Distinguish genuinely absent values from fields excluded by the integration’s readable scope, and keep the output administrative.

Start with a employee-attribute completeness review that the HR data owner can check against the original records. Righthand prepares the review artifact; the source application remains the operational record.

Establish the input route

Personio’s API guide says custom employee attributes are returned only within granted readable access and describes returned values as current, rather than scheduled or historical. Official Personio reference, checked October 6, 2026.

Have the HR owner identify the whitelisted fields and employee cohort in the source slice. A connected route should be checked against one permitted record. Supply field definitions with an approved extract so a blank label is not treated as proof of a missing employee attribute.

Check the current integration directory and Righthand setup documentation. A listed app does not establish every read or write action. For a connected route, verify the assigned account, available operation, object scope, and one permitted sample read. This guide also works from an explicitly supplied, approved extract; it does not require an unverified native operation. Keep credentials out of the article brief.

Worked input and output

These three records are synthetic illustrations, not customer results or a hands-on integration test.

The review should have separate categories for missing values, scope exclusions, and historical questions. PE42 prevents the owner from chasing an employee for information that the extract was not permitted to return. PE43 needs a historical source if the task asks when the move happened.

A complete first-run brief

Use an approved Personio employee extract and required-field checklist for October 12–16, 2026. Fields: employee reference, department, office, manager reference, custom attribute key, current value, readable-field list, extract time. At Monday 9 AM America/Los_Angeles, prepare a employee-attribute completeness review as source-linked Markdown in my private review thread. Preserve record identities and the extract timestamp. Group unresolved items by next action and responsible owner. Reviewer: HR data owner. Do not update employee attributes, change attendance, infer eligibility, evaluate performance, or make employment decisions. Result check: Inspect the readable-field list and match each completeness flag to a permitted current employee record.

A permitted preparation step does not authorize a consequential write or an external send. Resolve proposed changes through the app's supported process after the responsible owner approves their exact scope.

Reconcile before widening the task

Custom attribute labels can change while their technical keys remain stable. Preserve both in the review and avoid matching only by display text. Current values alone cannot establish an absence history or a sequence of office changes; widen the evidence route only with HR approval.

Test one required-field checklist in the next HR housekeeping session. Ask the owner to explain PE42 without requesting unnecessary personal data. Accept the review when scope exclusions stay separate from actual completeness questions and current values are clearly dated.

For the first acceptance review, keep the original input slice beside the result and mark which items were checked. If access or evidence is incomplete, return that gap with its record identity rather than a confident completion statement. Review Pricing using the actual preparation workload and correction effort.