> 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/lucca.md).

# Lucca

Connect Lucca to Siit to sync your employee directory and lifecycle events. Lucca is widely used by French and European companies for HR, leave, and timesheet management.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2F60OLaa40MVYtUIP0aqXm%2FSiit_Lucca.jpg?alt=media&amp;token=54322ee2-4564-424e-a048-802b7e4690fc" alt=""><figcaption></figcaption></figure>

### What you get

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

### What syncs from Lucca

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

Work email is the canonical identifier across systems.

### Before you connect

* A Lucca admin to generate an API key.
* Work email populated for every active employee in Lucca.

### Connect Lucca

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

For the detailed walkthrough, see our Help Center guide: [Lucca integration setup](https://help.siit.io/lucca-integration).

### After the connection

* Confirm your **People list** matches your active + upcoming Lucca employees.
* In **Settings → Context management → People fields**, set Lucca 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

Lucca 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 Lucca.

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

**"Invalid credentials" on connect.** The API key was revoked. Generate a new one in Lucca 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/lucca.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.