> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kombo.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# Emply People ATS Integration
> Emply People connector for Kombo's ATS API
This connector is in closed beta. Please contact us to get access.
The Emply People ATS integration allows you to sync ATS data between Emply People and your application through Kombo's unified API. The tool slug for this connector is `emplypeople`.
## Guides and Resources
Step-by-step instructions to connect your Emply People account to Kombo.
## General Notes
* Emply People returns at most 50 vacancies and its `/vacancies` pagination is broken, so only the first page syncs. Jobs, job postings and the applications on any vacancy beyond that page are not available.
* Applications only sync when jobs are enabled. Emply People gives no way to tell whether an application belongs to a job or to a talent pool without reading the vacancies.
## Supported Features & Coverage
Emply People uses the same accounts for HR and recruiting, so users include people who are not involved in recruiting. They cannot be filtered out, because roles are named freely in Emply People.
| Field | Notes |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| first\_name | |
| last\_name | |
| email | |
| status | A user is `ACTIVE` while their Emply People login is active, which is the only signal Emply People exposes. Users deleted in Emply People are not synced at all. |
| remote\_data | |
Only synced for public application forms
| Field | Notes |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| name | |
| job\_code | |
| description | |
| status | A vacancy has no status of its own in Emply People, only its publishings do. `status` is therefore derived from those, and a vacancy that was never published doesn't have one. |
| department | |
| location | |
| custom\_fields | Job details (the extra fields shown on a vacancy in Emply People) are not reported as custom fields yet. A vacancy carries their values without their names, and the names live on the vacancy template, which Kombo does not read yet. |
| integration\_fields | |
| closed\_at | |
| remote\_created\_at | |
| remote\_updated\_at | |
| contact\_id | |
| remote\_data | |
A publishing has no id of its own in Emply People, so `remote_id` is built as `{vacancyId}:{mediaId}`. A vacancy is published to a channel at most once, so that pair is unique.
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| title | |
| description\_html | |
| status | |
| url | |
| job\_id | |
| remote\_data | |
A candidate in Emply People is only a name, an email and a list of applications. Everything else the candidate provided lives on the application form.
A candidate can have no applications at all. Emply People talent pools are not synced as jobs, so candidates who only ever joined a pool have none.
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| first\_name | |
| last\_name | |
| phone\_numbers | |
| email\_addresses | |
| integration\_fields | |
| remote\_created\_at | |
| remote\_updated\_at | |
| remote\_data | |
Emply People doesn't provide application stages, so we derive them from applications. A stage without applications is therefore not visible, and a stage that temporarily holds none is marked as deleted until an application moves back into it. Stages are connected to the jobs they were seen on.
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| name | |
| remote\_data | |
| Field | Notes |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| outcome | Emply People doesn't provide an application status, so we derive `outcome` ourselves. An application is `DECLINED` once it has a disqualification reason. Emply People marks no pipeline stage as the final one, so `HIRED` is derived from the name of the stage the application sits in. Applications in a renamed hired stage stay `PENDING` instead of being guessed as hired. |
| rejection\_reason\_name | |
| current\_stage\_id | |
| job\_id | |
| candidate\_id | |
| screening\_question\_answers | Answers to the questions configured directly on a vacancy are not available in Emply People. The questions themselves are still reported on the job. A file-type question's answer carries no download URL: Emply People's API exposes an attachment's name and type, but offers no way to download it. |
| custom\_fields | |
| integration\_fields | |
| remote\_created\_at | |
| remote\_updated\_at | |
| remote\_data | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| title | |
| description | |
| format | |
| remote\_data | |
Emply People doesn't provide a list of disqualification reasons, so we derive them from disqualified applications. Reasons that have never been used are not available.
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| name | |
| remote\_data | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| remote\_label | |
| scope | |
| unified\_type | |
| Field | Notes |
| ------------------- | ----- |
| index | |
| job\_id | |
| stage\_id | |
| id | |
| changed\_at | |
| remote\_deleted\_at | |
| Field | Notes |
| -------------------------- | ----- |
| index | |
| required | |
| precondition\_question\_id | |
| precondition\_options | |
| job\_id | |
| question\_id | |
| id | |
| changed\_at | |
| remote\_deleted\_at | |
Only a vacancy's project manager syncs as its hiring team, and without a role. Emply People's own team list is not read yet.
| Field | Notes |
| ------------------- | ----- |
| id | |
| changed\_at | |
| remote\_deleted\_at | |
| Field | Notes |
| ------------------- | ----- |
| roles | |
| job\_id | |
| user\_id | |
| id | |
| changed\_at | |
| remote\_deleted\_at | |
Only **Administrator**, **Hiring Manager** and **Recruiter** are mapped. Custom and renamed roles have no type.
| Field | Notes |
| ------------------- | ----- |
| user\_id | |
| role\_id | |
| id | |
| changed\_at | |
| remote\_deleted\_at | |
The job application form must include an email address field. Emply People ignores answers for fields that are not on the form, so without it the application cannot be created.
| Input Field | Notes |
| ----------------------------------------- | ----- |
| candidate.first\_name | |
| candidate.last\_name | |
| candidate.email\_address | |
| candidate.phone\_number | |
| application.job\_id | |
| application.stage\_id | |
| screening\_question\_answers.question\_id | |
| screening\_question\_answers.answer | |
| attachments.name | |
| attachments.content\_type | |
| attachments.data\_url | |
| attachments.data | |
| attachments.type | |
| source.name | |
The job application form must include an email address field. Emply People ignores answers for fields that are not on the form, so without it the application cannot be created.
| Input Field | Notes |
| ----------------------------------------- | ----- |
| candidate.first\_name | |
| candidate.last\_name | |
| candidate.email\_address | |
| candidate.phone\_number | |
| application.job\_id | |
| application.stage\_id | |
| screening\_question\_answers.question\_id | |
| screening\_question\_answers.answer | |
| attachments.name | |
| attachments.content\_type | |
| attachments.data\_url | |
| attachments.data | |
| attachments.type | |
| source.name | |
| Feature | Notes |
| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| API Passthrough | |
| Scope Testing | |
| Per Model Tests | |
| Source Writing | |
| Sync Only Created Applications | |
| Connection Guide | |
| Roles | |
| System roles (e.g. Admin) | Only **Administrator**, **Hiring Manager** and **Recruiter** are mapped. Custom and renamed roles have no type. |
| Job roles (e.g. Hiring Manager) | Only a vacancy's project manager syncs as its hiring team, and without a role. Emply People's own team list is not read yet. |