Integrations

Personio integration for AI agents

Look up employees, manage absences, and track attendance

Connect Personio to Langdock and use it in chat, in agents and in workflows.

49 actions

Personio actions

Each action is one step an agent or workflow can run in Personio.

  • Create absence period

    Creates an absence period. For a daily absence, ends_at is midnight at the start of the day after the last absence day. When the response includes the period, report calendarAbsence.firstDate through calendarAbsence.lastDate, with startsOn and endsOn for half days. For an hourly absence, report calendarAbsence.startsAt and calendarAbsence.endsAt. If lastDate is null, the absence is ongoing and has no end day.

  • Create attendance

    Create a new attendance entry for an employee.

  • Create compensation

    Creates a compensation for an employee (one-time, recurring, fixed, or hourly). Bonuses not supported.

  • Create compensation type

    Creates a new compensation type that can be used when creating compensations.

  • Create person

    Create a new person and employment.

  • Delete absence period

    Deletes an absence period by ID.

  • Delete attendance period

    Delete an attendance period by ID.

  • Delete document

    Deletes one employee document. Pick the owner, then the document.

  • Delete person

    Delete a person.

  • Get absence period

    Retrieves an absence period by ID. Get the ID from List absence periods or Create absence period. For a daily absence, ends_at.date_time is midnight at the start of the day after the last absence day. Report calendarAbsence.firstDate through calendarAbsence.lastDate, and startsOn and endsOn for half days. For an hourly absence, report calendarAbsence.startsAt and calendarAbsence.endsAt. If lastDate is null, the absence is ongoing and has no end day.

  • Get absence period breakdowns

    Retrieves daily breakdowns for an absence period.

  • Get absence type

    Retrieves an absence type by ID.

  • Get application

    Retrieve a recruiting application by ID.

  • Get application stage transitions

    Get the history of stage transitions for a recruiting application.

  • Get attendance

    Get attendance records with date range and employee filtering.

  • Get attendance period

    Retrieve a single attendance period by ID.

  • Get candidate

    Retrieve a recruiting candidate by ID.

  • Get custom attributes

    Get the list of custom attributes defined in Personio.

  • Get custom report

    Gets the rows of a custom report.

  • Get employment

    Retrieve a single employment by ID.

  • Get job

    Retrieve a recruiting job by ID.

  • Get job category

    Retrieve a recruiting job category by ID.

  • Get legal entity

    Retrieves a single legal entity by ID.

  • Get org unit

    Retrieves an organizational unit (team or department) by ID. Get org unit IDs from list_employments or get_employment responses.

  • Get person

    Retrieve a single person by ID.

  • Get time off balance

    Get the time off balance for a person.

  • Get time off types

    Get all available time off types.

  • List absence periods

    Returns absence periods. For a daily absence, ends_at.date_time is midnight at the start of the day after the last absence day, so that date is not itself an absence day. Report calendarAbsence.firstDate through calendarAbsence.lastDate, and startsOn and endsOn for half days. For an hourly absence, report calendarAbsence.startsAt and calendarAbsence.endsAt. If lastDate is null, the absence is ongoing and has no end day.

  • List applications

    Get a list of recruiting applications with optional filters.

  • List candidates

    Get a list of recruiting candidates with optional filters.

  • List compensation types

    Returns a list of compensation types including one-time and recurring types.

  • List compensations

    Returns payroll compensations including salary, hourly, one-time, recurring, and bonuses.

  • List cost centers

    Get a list of cost centers with filtering, sorting, and pagination.

  • List custom reports

    Lists custom reports saved in Personio.

  • List document categories

    Lists the employee document categories in this Personio company. Each category ID is specific to the company and is required when uploading a document to an employee. These are not recruiting file categories such as cv or cover-letter.

  • List documents

    Lists the metadata of documents belonging to the provided owner ID.

  • List employments

    List employments of a given person.

  • List job categories

    Get all recruiting job categories.

  • List jobs

    Get a list of recruiting jobs with optional filters.

  • List legal entities

    Returns a list of legal entities for the company, sorted by creation date.

  • List org units

    Lists departments or teams.

  • List persons

    Get a list of persons with optional filters.

  • List workplaces

    Get a list of workplaces with filtering, sorting, and pagination.

  • Search person by email

    Find a person by their email address.

  • Update absence period

    Updates an absence period by ID. For a daily absence, ends_at is midnight at the start of the day after the last absence day. When the response includes the period, report calendarAbsence.firstDate through calendarAbsence.lastDate, with startsOn and endsOn for half days. For an hourly absence, report calendarAbsence.startsAt and calendarAbsence.endsAt. If lastDate is null, the absence is ongoing and has no end day.

  • Update attendance period

    Update an attendance period by ID.

  • Update employment

    Update an employment record.

  • Update person

    Update a person's information.

  • Upload document

    Uploads one finished file onto an employee profile in Personio. Use List persons for the employee ID and List document categories for the category ID. This does not fill a Personio template and does not attach the file to a recruiting application. Personio accepts common types such as PDF and DOCX, up to 30 MB.

Setup and permissions

An action can ask for your confirmation before it runs. In an agent, each action is set to “Always allow” or “Needs approval”.

All integrations