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

Connection Setup Guide

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

Models

Users

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

Jobs

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

Job postings

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

Candidates

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

Application Stages

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

Applications

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

Screening questions

Field	Notes
id
remote_id
changed_at
remote_deleted_at
title
description
format
remote_data

Rejection reasons

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

Roles

Field	Notes
id
remote_id
changed_at
remote_deleted_at
remote_label
scope
unified_type

Job-specific application stages

Field	Notes
index
job_id
stage_id
id
changed_at
remote_deleted_at

Job-specific screening questions

Field	Notes
index
required
precondition_question_id
precondition_options
job_id
question_id
id
changed_at
remote_deleted_at

Job user role assignments

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

Job hiring team members

Field	Notes
roles
job_id
user_id
id
changed_at
remote_deleted_at

User roles

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

Actions

Create candidate

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

Create application

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

Features

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.