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

# Factorial

> Connect Factorial to your Atako agents — 13 read and 1 write actions.

Let your agents look up employees, teams, locations and legal entities in Factorial, check time off, shifts, job roles, document metadata and expense reports, and file leave requests.

## Connection

* **Authentication**: API key.

<Note>
  Sign in to Factorial as an admin → Settings → Advanced section → API Keys → Create new API Key → enter a Name, pick an expiration (new keys expire after 24 hours by default: choose a longer period or a non-expiring key, otherwise the connection stops working the next day) → Get my API key, and copy it. Only admins can create keys; a key gives full access to the company account (Factorial has no per-key permissions).

  See [Factorial's documentation](https://help.factorialhr.com/en_US/how-to-create-api-keys).
</Note>

## Read actions (13)

| Action | Description |
| - | - |
| `get_employee` | Fetch one employee by ID (IDs come from list\_employees), with the same fields as list\_employees — identity, bank, personal-contact and birth fields removed. |
| `list_document_folders` | List document folders, optionally by name, active state or employee. |
| `list_documents` | List document metadata (file name, type, size, folder, employee, signature status) — never the file content — optionally by employees, folder (from list\_document\_folders), leave (from list\_leaves), trash bin or pending assignment. |
| `list_employees` | List employees (paginated, max 100 per page): id, names, login\_email, communications\_email, company / legal entity / location / manager ids, city, country, seniority, active and termination fields — national id, social security number, bank details, personal e-mail and phone, emergency contact, home address and birth details are removed. Optional filters: full\_text\_name, name\_starts\_with, emails (array of employee e-mails), team\_ids, location\_ids, legal\_entity\_ids (arrays of ids), only\_active, only\_managers (booleans), updated\_at\_gteq (YYYY-MM-DD), limit (1–100), after\_id / before\_id (cursors). |
| `list_expensables` | List expense reports (expenses, mileages, per diems) with amount, currency and status, optionally by employees, statuses, a date window (from/to) or a text search. |
| `list_job_levels` | List the job levels of the job catalog, optionally for given role IDs (from list\_job\_roles). |
| `list_job_roles` | List the job roles of the job catalog. |
| `list_leave_types` | List the leave (time off) types, optionally only active or payable ones, or those available to an employee. |
| `list_leaves` | List leaves (time off), optionally filtered by employees, leave types, a date window (from/to, YYYY-MM-DD), approval state; can include pending or deleted leaves and their duration. |
| `list_legal_entities` | List the legal entities of the company (legal name, country, currency). |
| `list_locations` | List company locations (workplaces), optionally only the main one. |
| `list_shifts` | List attendance shifts (clock-in/clock-out), optionally for given employees, a date window (start\_on/end\_on, YYYY-MM-DD), workable days, the latest shift per employee, or a last-update date. |
| `list_teams` | List teams with their member and lead employee IDs. |

## Write actions (1)

| Action | Description |
| - | - |
| `create_leave` | Create a leave request for an employee. It follows the approval flow of its leave type in Factorial; this connector has no approve/reject action. Arguments: employee\_id (string ID from list\_employees, required), start\_on (string YYYY-MM-DD, required), finish\_on (string YYYY-MM-DD, optional), leave\_type\_id (string ID from list\_leave\_types, optional), description (string, optional), start\_time (string HH:MM, optional, for a partial day), hours\_amount\_in\_cents (integer, hours × 100, e.g. 800 = 8 h, optional). |

## Permissions

Every action above must be explicitly granted to an agent before it can be used. See [Permissions](/integrations/permissions) for the grant model and [Security](/integrations/security) for how credentials are protected.

***

*Last reviewed against the provider API: September 2026.*


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