ATS Coverage Matrix

​

Overview

This document provides a standardized view of what features each ATS client supports. Use this reference to understand the capabilities and limitations of each integration. We currently support 20 ATS integrations with varying levels of feature coverage. Each ATS is categorized by its implementation approach.

​

Implementation Approaches

​

Kombo-based Integrations

These integrations leverage the Kombo unified API, which provides standardized access to ATS systems. Most core functionality is automatically inherited.

• Greenhouse
• Jobvite
• Bullhorn
• Crelate
• JobDiva
• Avionte
• SuccessFactors
• Workday
• UKG Ready
• Workable
• Paradox (open beta Kombo connector)
• Paylocity (jobs-only via Kombo)
• Paycor (read-only via Kombo, open beta connector)

​

Direct API Integrations

These integrations connect directly to the ATS provider’s API, requiring full implementation of all methods.

• ERecruit
• RecruitCRM
• Tracker
• TempWorks
• LiveHire
• Public API

​

Hybrid Integrations

These combine multiple data sources or approaches for specific customer needs.

• Tracker Workable (MW Resources)

​

Limited Coverage Integrations

• Paylocity (Kombo): Supports job streaming only. Applications, candidates, stage movement, notes, and attachments are not available through Kombo for this connector.
• Paycor (Kombo): Read-only by design. Jobs, candidates, and applications stream in, and application stages are read natively via passthrough (Kombo returns none), but every write path (application/candidate creation, stage moves, rejection, notes, attachments, custom fields) is explicitly blocked — see Paycor ATS.

​

Feature Coverage Matrix

The table below shows high-level feature support for a subset of ATS integrations. Integrations listed above that have no column (including Paradox) are documented on their own pages. Click an ATS name in the table for method-level coverage.

​

Legend

Supported - Feature is fully implemented and tested Partial - Feature is partially implemented or has known limitations Not Supported - Feature is not implemented or not applicable

​

Core Features

​

TempWorks Caveats

• Job and application streaming, direct detail lookup, batch job reads, and dynamic stage retrieval are implemented. Their read contracts have been verified against Surge, but Employnet validation remains pending its credentials.
• Stage movement is implemented and unit tested against the exact Job Order Candidate identity. No live status write has been made.
• Candidate streaming and candidate attachments apply to the existing Surge extension. Interview summaries for the standard TempWorks Cloud application flow are written to the associated Employee’s message history when a tenant-specific Message Action is configured and permitted.
• Candidate and job custom-field definitions are readable, Job Order custom-field values are readable, and candidate and job writes use their matching custom-data endpoints. Application custom fields are unsupported.
• Job Order Candidate comments and attachments are not used for interview results. Interview summaries use Employee Contact Messages, and interview PDFs use Employee documents.
• See TempWorks ATS for the standard-flow rollout gates and the Surge-specific behavior.

​

LiveHire Caveats

• LiveHire is a direct Humanforce Talent API integration (not Kombo). Jobs and candidates sync via webhooks; applicants are polled on a 5-minute cron for Tenzo-synced jobs.
• create_application assigns an existing LiveHire candidate to a job vacancy (POST /job-vacancies/{id}/assign); Tenzo does not create new candidates in LiveHire.
• Resume fetch uses candidate CVs only for now. Application CV download (GET /job-applications/{id}/cv/contents) is disabled because Challenger credentials get IAM 403; re-enable when LiveHire grants that scope.
• Custom field writebacks are not implemented. Job custom-field catalog for rules is discovered by unioning custom_field_values from the enhanced job cache; there is no LiveHire definitions API. Job analytics “additional fields” enrichment is also not implemented yet (missing LiveHire permissions on /analytics/job-vacancies-additional-fields).
• Notes, attachments, rejections, and optional unsuccessful notifications require a recruiter email resolved from the job or candidate.

​

Tracker Caveats

• Tracker and Tracker Workable resume fetch only accepts primary resume documents (documentType == "resume" and isPrimary).
• Tracker and Tracker Workable do not implement reject_application / bulk_reject_applications yet; stage movement is the supported workflow action.

​

UKG Ready Caveats

• UKG Ready application custom-field writebacks are routed to Applicant custom fields; no native Job Application custom-field write path is currently supported.
• UKG Ready job custom fields are readable for filtering/rules, but job custom-field writeback is not currently supported.
• See UKG Ready for setup steps, native enrichment details, and the full gotcha list.

​

Detailed Coverage

For method-level details, limitations, and implementation notes, see the individual ATS pages:

​

Related Documentation

• ATS Integration Checklist - Complete checklist for adding new ATS integrations
• ATS Integrations Overview - User-facing documentation for ATS setup