Atlas ATS Integration

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

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

Guides and Resources

Connection Setup Guide

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

General Notes

Atlas is an agency ATS. Projects map to jobs; people attached to projects (candidates) map to applications. Only people who appear on at least one project are synced as candidates.

Supported Features & Coverage

Models
Actions
Features

Users

GET /users only returns active Atlas team members. Users who have left, been deactivated, or are automated accounts are still created from note authors, interview attendees, and project members using the name and email on those payloads.

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
job_code
description
employment_type
status	Atlas project states `lead`, `pitch`, `opportunity`, and `talent_pool` map to `DRAFT`. `on_hold` maps to `CLOSED`.
visibility
experience_level
remote_work_status
location
custom_fields
integration_fields
closed_at
remote_created_at
remote_updated_at

Candidates

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

Application Stages

Field	Notes
id
remote_id
changed_at
remote_deleted_at
name
status

Applications

Field	Notes
id
remote_id
changed_at
remote_deleted_at
outcome
rejection_reason_name
rejected_at
current_stage_id
job_id
candidate_id
custom_fields
integration_fields
remote_created_at
remote_updated_at

Interviews

Field	Notes
id
remote_id
changed_at
remote_deleted_at
title
starting_at
ending_at
location
video_conferencing_url
application_id
canceled
remote_created_at
remote_updated_at

Offers

Field	Notes
id
remote_id
changed_at
remote_deleted_at
status
employment_start_date
application_id
custom_fields
integration_fields
remote_created_at
remote_updated_at

Roles

Field	Notes
id
remote_id
changed_at
remote_deleted_at
remote_label
scope
unified_type

Notes

Notes are attached to people (not applications). We ingest manual notes and phone-call notes from POST /people/notes/lookup; application_id is always unset. On delta syncs, a note is only picked up if the candidate it was added to also changed since the last sync. To get all notes, use a full sync.

Field	Notes
id
remote_id
changed_at
remote_deleted_at
candidate_id
author_id
content_html
remote_created_at
remote_updated_at

Job-specific application stages

Field	Notes
index
job_id
stage_id
id
changed_at
remote_deleted_at

Job user role assignments

Atlas assigns each project member a member type.

lead maps to RECRUITER
member syncs without a unified role type.

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

Interviewing team members

Field	Notes
interview_id
user_id
id
changed_at
remote_deleted_at

Create candidate

If a person with the same email, phone, or LinkedIn already exists in Atlas, the existing person is reused and their profile is not updated. Attachments are stored on the person, not on the candidate/application. CV attachments are uploaded as Atlas resume; COVER_LETTER and OTHER as other. Creates are attributed to the Atlas user configured in “Default user email for created people”. Atlas rejects writes when the project is closed or on hold. LinkedIn social links are stored as Atlas linkedin identities; other social links as website.

Input Field	Notes
candidate.first_name
candidate.last_name
candidate.email_address
candidate.additional_email_addresses.email_address
candidate.company
candidate.title
candidate.phone_number
candidate.additional_phone_numbers.phone_number
candidate.location.city
candidate.location.country
candidate.location.state
candidate.location.street_1
candidate.location.zip_code
candidate.gender
candidate.social_links.url
application.job_id
application.stage_id
attachments.name
attachments.content_type
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.additional_email_addresses.email_address
candidate.company
candidate.title
candidate.phone_number
candidate.additional_phone_numbers.phone_number
candidate.location.city
candidate.location.country
candidate.location.state
candidate.location.street_1
candidate.location.zip_code
candidate.gender
candidate.social_links.url
application.job_id
application.stage_id
attachments.name
attachments.content_type
attachments.data_url
attachments.data
attachments.type
source.name
source.unified_key
source.id

Add attachment to application

Atlas stores attachments on the person (candidate), not on a specific candidate/application. CV attachments are uploaded as Atlas resume (CV parsing runs when attached to a person). COVER_LETTER and OTHER are uploaded as other.

Input Field	Notes
application_id
attachment.name
attachment.content_type
attachment.data_url
attachment.data
attachment.type

Move application to stage

Moving uses Atlas stage IDs and places the candidate at the first status of that stage. Atlas rejects writes when the project is closed or on hold. A rejected candidate cannot be moved until the rejection is rolled back first.

Input Field	Notes
application_id
stage_id

Get application attachments

Atlas stores attachments on the person (candidate), not on a specific candidate/application. This returns all files attached to the candidate.

Input Field	Notes
application_id

Get candidate attachments

Atlas stores attachments on the person. Application-specific attachment links are not available, so application_id is always null.

Input Field	Notes
candidate_id

Feature	Notes
API Passthrough
Upstream Webhooks	project.created: triggered when a project (job) was created project.updated: triggered when a project (job) was updated including being published or unpublished candidate.stageMoved: triggered when an application stage changed, or a candidate was created when newly added to a project candidate.rejected: triggered when a candidate was rejected from a project pipeline person.updated: triggered when a person (candidate profile) was updated person.created: triggered when a person was created (only applied when they are already on a project) placement.created: triggered when a placement (hire / accepted offer) was created placement.updated: triggered when a placement (hire / accepted offer) was updated Not covered: screening questions updated on a job Not covered: tag assigned to a candidate Not covered: interview scheduled Not covered: interview updated Not covered: person experience created or updated (use person.updated for profile fields) Not covered: person contact created or updated on a company Webhooks are configured manually in Atlas (Settings → Integrations → Webhooks) and delivered via Svix. Not covered: notes created or updated on people. Not covered: client, contract, or financial fee events (no matching Kombo ATS models).
Scope Testing
Per Model Tests
Delta Syncs
Source Writing
Sync Only Created Applications
Connection Guide
Roles
Job roles (e.g. Hiring Manager)	Atlas assigns each project member a member type.

lead maps to RECRUITER
member syncs without a unified role type. |

General

Features

Guides

ATS API Reference

General API Reference

Atlas ATS Integration

Guides and Resources

Connection Setup Guide

General Notes

Supported Features & Coverage

​Guides and Resources

Connection Setup Guide

​General Notes

​Supported Features & Coverage

Guides and Resources

General Notes

Supported Features & Coverage