Phenom ATS Integration

This connector is in open beta. You can freely enable it in your account.

The Phenom ATS integration allows you to sync ATS data between Phenom and your application through Kombo’s unified API. The tool slug for this connector is phenom.

Guides and Resources

Connection Setup Guide

Step-by-step instructions to connect your Phenom account to Kombo.

Supported Features & Coverage

Models
Actions
Features

Users

Field	Notes
id
remote_id
changed_at
remote_deleted_at
first_name
last_name
email

Jobs

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
description
employment_type
status
visibility
category
department
post_url
location
custom_fields
integration_fields
opened_at

Candidates

Field	Notes
id
remote_id
changed_at
remote_deleted_at
first_name
last_name
company
title
source
phone_numbers
email_addresses
location
custom_fields
integration_fields

Applications

The Phenom API returns applications whose jobId references jobs that are not visible under siteType=external (internal, closed, or deleted jobs) or the placeholder value JOBID. Such applications are still ingested, but their job_id relation will be left dangling (the job will not exist in Kombo).

Field	Notes
id
remote_id
changed_at
remote_deleted_at
outcome
job_id
candidate_id
custom_fields
integration_fields

Roles

Field	Notes
id
remote_id
changed_at
remote_deleted_at
remote_label
scope
unified_type

Job user role assignments

Each job may include hiringManagerEmail, hiringManagerName, and multiRecruiter. User remote ids are the email addresses; Kombo adds the hiring manager first when hiringManagerEmail is set, then each recruiter with a non-empty recruiterEmail in list order.

hiringManagerEmail maps to unified type HIRING_MANAGER
Each multiRecruiter entry with a non-empty recruiterEmail maps to unified type RECRUITER

Field	Notes
job_user_id
role_id
id
changed_at
remote_deleted_at

Job hiring team members

Field	Notes
roles
job_id
user_id
id
changed_at
remote_deleted_at

Create candidate

Input Field	Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.phone_number
candidate.location.city
candidate.location.country
application.job_id
attachments.name
attachments.data_url
attachments.data
attachments.type
source.name
source.unified_key
source.id

Create application

Input Field	Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.phone_number
candidate.location.city
candidate.location.country
application.job_id
attachments.name
attachments.data_url
attachments.data
attachments.type
source.name
source.unified_key
source.id

Feature	Notes
API Passthrough
Scope Testing
Per Model Tests
Source Writing
Sync Only Created Applications
Connection Guide
Roles
Job roles (e.g. Hiring Manager)	Each job may include hiringManagerEmail, hiringManagerName, and multiRecruiter. User remote ids are the email addresses; Kombo adds the hiring manager first when hiringManagerEmail is set, then each recruiter with a non-empty recruiterEmail in list order.

hiringManagerEmail maps to unified type HIRING_MANAGER
Each multiRecruiter entry with a non-empty recruiterEmail maps to unified type RECRUITER |

Perview Pinpoint

⌘I

General

Features

Guides

ATS API Reference

General API Reference

Phenom ATS Integration

Guides and Resources

Connection Setup Guide

Supported Features & Coverage

​Guides and Resources

Connection Setup Guide

​Supported Features & Coverage

Guides and Resources

Supported Features & Coverage