> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/hris-and-ats/integrating-with-personio.md).

# Integrating with Personio

Sync Personio employee data into Drivetrain for headcount planning. Covers creating a custom integration and selecting the attributes to share.

Drivetrain uses Client ID and Secret of a custom integration created in Personio, it enables user to select the objects and fields they want to share.

[Prerequisites](#prerequisites)\
[Personio Setup](#personio-setup)\
[Generating API Credentials](#step-1-generating-api-credentials)

## Prerequisites

To connect Personio to Drivetrain, you need:

1. An active Personio admin account

## Personio Setup <a href="#personio-setup" id="personio-setup"></a>

### Step 1: Generating API Credentials

1. Log in to your Personio account and click on **Settings** in the bottom left.
2. Click **API Credentials** on Integrations Tile

![](https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-a8aacb434976560a72d96a81a7b3a1581d70b904%2FPS-1.png?alt=media)

3. Click **Create Custom Integration**
4. Enter name as **"Drivetrain Integration"** and click **Next.**

![](https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-6afd07486dc96d086ad40de37641a2f7ef8f5bab%2Fps-2.png?alt=media)

5. Under **Select the attributes you want to grant access rights for**, select the attributes you want to sync

{% hint style="info" %}
**Important:** To ensure the integration functions accurately, the following objects must be selected:

* Employees
* Attendances
* Absences
* Custom Reports
* Org Units
  {% endhint %}

6. Under Readable employee attributes, click select all or select the individual fields you want to sync.

Commonly used fields include:

* Email
* First name
* Last Name
* Gender
* Hire date
* Office
* Profile Picture
* Termination date
* Status
* Supervisor
* Occupation type (optional)

![](https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-6817061702f773d6a294c374787b519f8de10e75%2Fps-3.png?alt=media)

7. Click Create integration once done. You will then see your API Credentials populate. Copy and save these in a secure document.

![](https://4220329029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmBZR0D9lq6jrI895OuOU%2Fuploads%2Fgit-blob-f2a2d509bf0b17c1d7bcfa36f7b8f851cfab5566%2Fps-4.jpeg?alt=media)

{% hint style="info" %}
That's it, please share the Client ID and Client Secret via a secured link or doc to your Customer Success Manager
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://integrations.drivetrain.ai/integration-guide/readme/hris-and-ats/integrating-with-personio.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
