> ## Documentation Index
> Fetch the complete documentation index at: https://docs.famulor.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Personio

> Connect Personio to Automations with your own Personio API credential, with no sign-in window

Connect Personio to read your HR data in automations: people, employments, absences, attendances, projects and documents. Personio has no sign-in window for other apps. Instead you create an API credential in your Personio account and paste its Client ID and secret into Famulor.

What you get: the Personio **actions** in the [App Catalog](/automations/app-catalog). They all read data; Personio offers no triggers here.

| Action | What it returns |
| - | - |
| List persons | Current people, filtered by identity, status or creation date |
| List person employments | Employment records of one person, including status, type and working hours |
| List absence periods | Absence periods filtered by person, absence type or date range |
| List absence types | The absence types configured for your company |
| List attendance periods | Attendance periods filtered by people, projects, status or dates |
| List projects | Time-tracking projects |
| List documents | Document metadata for one owner, optionally by category and date |
| List document categories | The document categories and their IDs |
| List employee attributes | The standard and custom employee attributes the credential can read |
| List employee records | Employee records with the attributes you choose |

## Before you start

* You are a Personio user with **API access rights**. Without them, Personio does not let you create API credentials.
* Your Famulor workspace has the Automation platform on its plan, and you are an owner or admin of the workspace.

Client ID and secret stay at the app connector; Famulor never stores them in your workspace.

## Step 1 — Create an API credential in Personio

1. In Personio, open **Marketplace → Connected integrations** and go to **API credentials**.
2. Create a new credential and give it a name you will recognize, for example *Famulor*.
3. Turn on **read access** for the data your automations need. **Persons** is required, because Famulor uses it to check the connection. Add absences, attendances, projects, documents and employee attributes if you want to use those actions.
4. Save, then copy the **Client ID** and the **Client secret**. Personio shows the secret only once. If you lose it, reset the credential and use the new pair.

## Step 2 — Connect in Famulor

1. Go to **Automations → Connections** and click **New connection**.
2. Open the **App marketplace**, search for **Personio** and select it.
3. Enter the **Client ID** and the **Client secret**. The connection name is optional; empty, it is called *Personio*.
4. Click **Connect Personio**.

Famulor checks the credential with Personio right away. On success the connection appears as **ok** in the Connections list, and the Personio actions are available in every automation of the workspace.

## Troubleshooting

| Message | What it means | Fix |
| - | - | - |
| *Personio rejected the Client ID or secret* | A typo, or the secret was reset in Personio. | Copy both values again, or reset the credential and use the new pair. |
| *Personio accepted the credentials but they cannot read employees* | The credential has no read access to persons. | Edit the credential in Personio, turn on read access for persons, and connect again. |
| An automation step fails with a permission error | The credential lacks read access for that data. | Add the read access in Personio, then **Replace credentials** on the connection in Famulor. |

## Reconnecting and removing

* **Replace credentials:** open the connection under Automations → Connections and choose **Edit**. Enter the new Client ID and secret; Famulor replaces the stored credential in one step.
* **Remove:** deleting the connection also removes the credential from the app connector. Automations that used the connection show *Connect needed* until you connect Personio again.
* To revoke access on the Personio side, delete or reset the API credential in Personio.

## Related

* [App Catalog](/automations/app-catalog)
* [Automation node reference](/automations/nodes)
* [Automations overview](/automations/overview)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.