.webp)
Automate
recruiting workflows
across your HR systems
When a candidate is marked as hired, peopleIX automatically triggers the next steps — generate contracts, collect signatures, create employees in your HR system and notify hiring managers.
Join 30+ People Teams already leveraging
People Intelligence with peopleIX.

.webp)
.webp)

Recruiting processes are often fragmented
Recruiting usually involves multiple tools — from applicant tracking systems to HR platforms and document solutions. HR teams constantly switch between systems to move candidates through the hiring process.
This often leads to manual handovers, forgotten tasks and slower hiring processes.
peopleIX connects your recruiting and HR systems and automates the entire hiring workflow — from candidate to employee.
How peopleIX automates your hiring workflow
When a candidate is hired, peopleIX automatically coordinates the next steps across your systems.
From Candidate to Employee — Automatically
When a candidate’s status changes to “Hired” in your ATS, peopleIX launches the next steps automatically:
Examples:
- Contract generation
- Internal notifications
- HR system updates
Automatically Generate Employment Contracts
peopleIX creates contracts based on:
- Role
- Salary
- Location
- Contract type
Collect Digital Signatures Seamlessly
Contracts are sent directly to your e-signature platform. peopleIX handles:
- Sending
- Reminders
- Status tracking
Onboard Employees in Your HR System Automatically
Once a contract is signed, peopleIX creates the new employee in your HR system, transferring:
- Personal details
- Role and salary
- Contract information
FAQs
Questions about peopleIX?
We’re here to help! If you have any more questions, just get in touch with us.
Permissions in peopleIX are tied to roles, organizational contexts, and tenant assignments. The basis is the existing role concept, e.g., Admin, Full Member, and Limited Member. For restricted roles, access can be further controlled via data sources and custom filters, so that workflows only access the data and actions allowed within the respective context.
Workflow executions are linked to the respective user and organizational context. At the same time, data access follows the peopleIX role and permission model. Where necessary, access can be further restricted to specific data sources and filtered data areas, ensuring that workflows operate only within the intended functional scope.
peopleIX logs relevant information about workflow runs, including status, run times, and redacted inputs and outputs of individual steps. This ensures traceability for operations, analysis, and governance.
Sensitive integration configurations are stored encrypted. Credentials are not passed uncontrolled through workflows but are processed in secure execution contexts and redacted or excluded from logs.

.webp)