# Personio + Greenhouse integration > Stop re-entering candidate data by hand. Automate the flow between your ATS and HR platform so your teams can spend time on people instead of copy-paste. **Canonical page:** https://tray.ai/connectors/personio-greenhouse-integrations/ **Personio connector:** https://tray.ai/connectors/personio-integrations/ **Personio documentation:** https://tray.ai/documentation/connectors/service/personio **Greenhouse connector:** https://tray.ai/connectors/greenhouse-integrations/ **Greenhouse documentation:** https://tray.ai/documentation/connectors/service/greenhouse ## Overview Personio and Greenhouse cover different parts of the employee lifecycle — Greenhouse runs your recruiting process while Personio takes over once someone signs on. They're complementary by design, but without an integration, the handoff between them is manual, slow, and error-prone. Connecting them through tray.ai means every hire moves from offer accepted to employee onboarded without anyone touching a spreadsheet. When Greenhouse and Personio don't talk to each other, someone has to do the talking for them. Candidate details, job offers, start dates, compensation — all of it gets re-entered by hand, which means delays and mistakes right when it matters most. HR teams spend hours copying new hire data into Personio. Recruiters never find out where onboarding stands. Integrating the two through tray.ai fixes this. The moment an offer is accepted in Greenhouse, a Personio employee record exists. Job requisitions stay consistent across both platforms. People Ops can trigger onboarding the instant a hire is confirmed, not after a chain of emails and a spreadsheet handoff. ## Use cases ### Automatic Employee Creation on Hire When a candidate reaches the 'Hired' stage in Greenhouse, tray.ai creates a fully populated employee record in Personio — name, role, start date, salary, department — without anyone typing a thing. HR can start onboarding from day one without waiting on a recruiter to send over a file. - Eliminates duplicate data entry between recruiting and HR teams - Cuts the time between offer acceptance and HR record creation - Produces consistent, error-free employee data from the first record forward ### Syncing Job Requisitions from Personio to Greenhouse When a hiring manager approves a headcount request in Personio, tray.ai creates the corresponding job in Greenhouse — department, location, and job description included. Recruiters can start sourcing the moment a role is approved, not after someone manually sets it up in the ATS. - Cuts time-to-open for new roles by removing manual ATS setup - Ensures only approved headcount roles get opened in Greenhouse - Keeps department and org structure consistent across both platforms ### Onboarding Workflow Trigger on Hire Confirmation Once a candidate is marked as hired in Greenhouse, tray.ai kicks off a structured onboarding workflow in Personio — task lists assigned, hiring manager notified, pre-boarding communications scheduled. No onboarding step gets missed, and new hires aren't left wondering what happens next before their first day. - Standardizes onboarding across every new hire regardless of department - Notifies relevant stakeholders automatically at the moment of hire - Reduces the risk of missed onboarding tasks or delayed system access ### Rejected Candidate Status Updates When a candidate is rejected or a role closes in Greenhouse, tray.ai updates or archives the related records in Personio. Headcount planning data stays accurate, ghost requisitions don't pile up, and finance teams get a reliable view of open versus filled roles. It also helps manage candidate data retention for GDPR compliance. - Keeps workforce planning data clean and current - Supports GDPR data retention policies across both platforms - Prevents open headcount mismatches between Greenhouse and Personio ### Offer Details and Compensation Sync When an offer is approved and accepted in Greenhouse, tray.ai moves the compensation details — base salary, bonus, employment type, start date — directly into the corresponding Personio employee record. No manual transcription, no risk of a number getting changed in transit. Payroll teams in Personio have accurate salary data before the employee ever shows up. - Eliminates compensation transcription errors during the recruiter-to-HR handoff - Gives payroll teams accurate salary data before the employee's start date - Creates a clear audit trail of offer details linked to the employee record ### Probation Period Setup from Greenhouse Hire Date Using the confirmed start date from Greenhouse, tray.ai sets up probation period milestones and reminders in Personio for each new hire. HR managers get automated alerts before review dates, and employees are notified of expectations through Personio's task and document features. - Automates probation milestone setup based on confirmed start dates - Ensures managers get timely reminders for performance check-ins - Connects recruiting outcomes directly to the performance management lifecycle ### Headcount Reporting Across Both Platforms tray.ai can pull pipeline and headcount data from both Greenhouse and Personio into unified workforce reporting dashboards. Recruiting velocity, offer acceptance rates, onboarding completion — all in one view, synced on a schedule. People Ops leaders get the cross-platform visibility they need to make real hiring and retention decisions. - Unified headcount and pipeline visibility across recruiting and HR - Combined Greenhouse and Personio metrics in one place - Less manual reporting work for People Ops and HR analytics teams ## Templates ### Hired Candidate to Personio Employee Record Automatically creates a new employee record in Personio when a candidate moves to the 'Hired' stage in Greenhouse, mapping personal, role, and compensation fields across. Connectors used: Greenhouse, Personio ### Personio Approved Headcount to Greenhouse Job Creation When a new position is approved in Personio, this template opens a corresponding job requisition in Greenhouse so recruiters can start sourcing without delay. Connectors used: Personio, Greenhouse ### New Hire Onboarding Workflow Kickoff Triggers a complete onboarding task sequence in Personio the moment a hire is confirmed in Greenhouse, including task assignments, manager notifications, and pre-boarding document requests. Connectors used: Greenhouse, Personio ### Daily Greenhouse-to-Personio Hire Sync Runs on a schedule to reconcile all newly hired candidates in Greenhouse with employee records in Personio, so no hires slip through and data stays consistent across both platforms. Connectors used: Greenhouse, Personio ### Offer Compensation Data Sync to Personio Maps approved offer details from Greenhouse — salary, employment type, and start date — into the corresponding Personio employee profile so compensation data is accurate from day one. Connectors used: Greenhouse, Personio ### Closed Role Sync and Headcount Reconciliation When a job closes in Greenhouse — filled or cancelled — this template updates the related headcount record in Personio to keep workforce planning data accurate and prevent stale requisitions from stacking up. Connectors used: Greenhouse, Personio ## Challenges Tray.ai solves ### Field Mapping Between Different Data Models Greenhouse and Personio use different data structures and terminology. What Greenhouse calls a 'candidate' with an 'application' becomes an 'employee' with a 'contract' in Personio. Department IDs, employment types, and custom fields rarely line up out of the box, so manual mapping is slow and easy to get wrong. **How Tray.ai helps:** tray.ai's data mapping and transformation tools let teams visually map fields between Greenhouse and Personio, apply conditional logic for different employment types, and normalize values like department names or contract types — no custom code required. ### Handling Duplicate Records Across Platforms Candidates who were previously in Personio as contractors or past employees may already have records. When a Greenhouse hire triggers a new employee creation, that means a real risk of duplicate profiles. Catching and cleaning these up manually is slow and easy to miss. **How Tray.ai helps:** tray.ai workflows check Personio for an existing record by email or employee ID before creating anything new. When a match is found, the workflow updates that profile instead of creating a duplicate. ### Webhook Reliability and Event Ordering Greenhouse webhooks can occasionally fire out of order or arrive late. An offer-accepted event might show up before the candidate record is fully populated, which means an incomplete employee record gets created in Personio — and someone on the HR team has to track down what's missing. **How Tray.ai helps:** tray.ai handles webhook ingestion with built-in retry logic and error handling. Workflows can pause, re-fetch complete data from the Greenhouse API, and only write to Personio once all required fields are confirmed present. ### GDPR and Data Privacy Compliance Across Borders Both platforms store sensitive personal data subject to GDPR and other regional privacy rules. Connecting them means making sure data flows respect consent records, retention policies, and regional data residency requirements — something generic integration tools tend to skip over. **How Tray.ai helps:** tray.ai provides enterprise-grade security controls including data encryption in transit and at rest, regional deployment options, and conditional workflow logic that respects GDPR consent flags and data minimization requirements when syncing candidate and employee data. ### Keeping Custom Fields in Sync as Schemas Evolve Both Greenhouse and Personio are highly configurable, and HR teams add custom fields regularly. When a new field appears on a job application or employee profile, rigid integrations break quietly — producing data gaps that go unnoticed until an audit surfaces them. **How Tray.ai helps:** tray.ai's workflow versioning and alerting let integration owners monitor for schema changes and get notified when unmapped fields show up. Updates are fast to make in the visual editor, so a new custom field in either platform doesn't mean rebuilding the integration from scratch. ## Learn more - Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/ - Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/ - Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/ - Book a demo: https://tray.ai/contact/