Humaans
Humaans is an HR system of record — the employee directory, plus the teams, companies, job roles and time off around it.
Authentication
- API key
Actions
Generic API request. Call any Humaans API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.
- Get person (v1)Retrieve a single person (employee) by id (GET /people/{personId}).
- List companies (v2)List the legal entities configured in the Humaans workspace, to resolve the company id a person record belongs to.
- List job roles (v1)List job roles across the Humaans account (GET /job-roles).
- List people (v1)List people (employees) in the Humaans account (GET /people).
- List teams (v1)List the teams configured across the Humaans account, to resolve a team id or to see how the organisation is grouped.
- List time away (v2)List time-away (leave) records in the Humaans workspace (GET /time-away).
Triggers
- New or updated companyStarts when a legal entity is added to the Humaans workspace or an existing one is edited, detected by polling GET /companies filtered by updatedAt since the last poll.
- New or updated job roleStarts when a job role assignment is created or edited in Humaans, detected by polling GET /job-roles filtered by updatedAt since the last poll.
- New or updated personStarts when a person record is added to the HR directory or an existing one is edited, detected by polling GET /people filtered by updatedAt since the last poll.
- New or updated time awayStarts when a leave request is booked or changes in Humaans, detected by polling GET /time-away filtered by updatedAt since the last poll — the exact pattern the provider's own docs describe.
- Person created or updated (webhook)Starts when a person record is created or updated in Humaans, delivered by a webhook instead of polling people for their updatedAt timestamp.
Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.