> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/integrations/hris/payfit.md).

# Payfit

Connect Payfit to Siit to sync your employee directory and lifecycle events. Payfit is a popular payroll and HR platform for European SMBs.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FDd3dvteH4jVTd4YQh36X%2FSiit_Payfit.jpg?alt=media&amp;token=8dddb522-1d1a-4b89-9800-e472e06e834e" alt=""><figcaption></figcaption></figure>

### What you get

* **Live People directory** — Payfit employees appear in Siit with role, manager, department, and lifecycle dates.
* **Lifecycle triggers** — Hire date, End date, and Birthday flow into Siit as workflow triggers.
* **Manager resolution** — Payfit's reporting structure powers auto‑selected approvers in workflows.
* **Pre‑hires** — future employees with a hire date in Payfit appear in Siit ahead of Day 1.

### What syncs from Payfit

| Category        | Fields                                         |
| --------------- | ---------------------------------------------- |
| Identity        | First name, last name, work email, employee ID |
| Role            | Job title, department                          |
| Org structure   | Manager, work location, company / legal entity |
| Employment      | Contract type, status                          |
| Lifecycle dates | Hire date, contract end date, date of birth    |

Work email is the canonical identifier. Compensation and payroll data are not synced into Siit.

### Before you connect

* A Payfit admin to generate API credentials.
* Work email populated for every active employee in Payfit.

### Connect Payfit

1. In Payfit, generate API credentials for Siit with read access to the employee directory.
2. In Siit, go to **Settings → Workspace → Integration library**, find **Payfit** in the HRIS section, and click **Connect**.
3. Enter the credentials, then click **Authorize**.
4. Review the imported people and field mapping, then click **Finish setup**.

Need a more detailed walkthrough? Reach out to support via the in‑app chat.

### After the connection

* Confirm your **People list** matches Payfit's active workforce.
* In **Settings → Context management → People fields**, set Payfit as the source of truth for HR‑owned fields if you're also connected to an IdP.
* Build a Day‑1 onboarding workflow using the Hire date trigger.

### Sync frequency

Payfit data refreshes automatically every few hours.

### Common workflows

**Day‑1 onboarding.** *Trigger: Hire date. Actions: create IdP account, assign apps by department, ship equipment, DM manager.*

**Offboarding on contract end.** *Trigger: Contract end date. Actions: revoke sessions, remove app access, equipment pickup, notify manager.*

### Troubleshooting

**Employees missing.** Only active employees and future hires sync by default. Confirm status and work email in Payfit.

**Manager field empty.** In Payfit, check the employee has a manager assigned on their profile.

**"Invalid credentials" on connect.** The credentials were revoked. Regenerate in Payfit and update Siit.


---

# 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://docs.siit.io/integrations/hris/payfit.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.