> ## Documentation Index
> Fetch the complete documentation index at: https://f4c7a9e2d8b1-docs.tenzo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# ADP Workforce Now ATS

> Initial feature coverage and limitations for the ADP Workforce Now integration

## Implementation overview

**Implementation type:** Kombo-based integration
**Status:** Foundation in development
**Initial mode:** Reads plus two application writebacks

ADP Workforce Now connects through Kombo's unified ATS API. The integration reuses the shared Kombo paths for reading jobs, applications, and candidates. It also posts the two Kombo-documented application writebacks: an interview-results PDF and a Tenzo result link.

Every other write stays blocked until Kombo documents the ADP action and the behavior is verified against an ADP-connected tenant. A generic Kombo method is not treated as ADP support on its own.

## Initial supported behavior

* Read jobs and fetch individual jobs through Kombo.
* Read applications and fetch applications by ID through Kombo.
* Read candidates and fetch or search candidates through Kombo.
* Read the application-stage catalog through Kombo.
* Read mapped application, candidate, and job custom-field schemas through Kombo.
* Read populated custom-field values from normalized Kombo job data.
* Use normalized Kombo job data for job caching and Rules Engine evaluation.
* Create a disabled-by-default ATS integration record when Kombo reports a new `adpworkforcenow` connection.
* Attach the interview-results PDF to the ADP application when Interview Results PDF is enabled.
* Post a Tenzo result link (and optional score and completion attributes) to the ADP application after a call.

All sync flags remain disabled when the integration is first created. They must be enabled deliberately after the connected tenant is ready for validation.

The two application writebacks follow the default post-call flags used by database-driven orgs: PDF posting is on unless Interview Results PDF is turned off, and the result link posts whenever the link flag is on. Validate both against a dummy Inland application before enabling interviews on real candidates.

## Explicitly blocked during the foundation phase

* Candidate and application creation
* Application stage movement
* Single and bulk rejection
* Disposition reasons
* Application, candidate, and job notes
* Candidate attachments
* Candidate resume retrieval through Kombo attachments
* Job, application, and candidate custom-field writes

These paths return safely without calling Kombo. This prevents inherited unified actions from becoming accidental ADP writes before their connector-specific behavior is verified.

## Known connector limitations

Kombo documents jobs, candidates, applications, and application stages for ADP Workforce Now. Its documented application-stage data is based on stages observed on applications, so it does not establish a complete selectable stage catalog.

Kombo documents application attachment and result-link actions for ADP Workforce Now, and this integration uses both. Failed Kombo writes now raise so the post-call worker can retry. Application PDF replacement is not supported, so a reprocessed call can leave a duplicate PDF on the application.

Kombo does not currently document ADP Workforce Now support for general stage movement, rejection, application creation, notes, candidate attachment retrieval, or candidate attachment upload. Kombo passthrough is not sufficient evidence by itself because it can only call operations exposed by the underlying ADP API.

## Configuration

The foundation configuration exposes:

* Start Stages as the inbound eligibility filter (which applicants Tenzo picks up). This is a read-only gate and does not write to ADP. Leave it empty to stop syncing new applicants; already-ingested lookups stay allow-all until a start stage is set.
* AI interview scoring thresholds
* Interview Results PDF attachments
* Automatic job activation and activation delay
* Syncing applicants for paused jobs

The Start Stages dropdown comes from Kombo's application-stage catalog, which is inferred from stages already observed on applications. A real start stage with no observed applications will not appear until one does.

Result-link posting follows the default post-call link flag rather than a separate ADP control. Write-side stage targets, disposition controls, notes, candidate attachments, and custom-field selectors remain unavailable until their underlying operations are supported and verified.

## Validation required before enablement

1. Connect an ADP Workforce Now test tenant through Kombo.
2. Confirm jobs, applications, and candidates can be streamed and fetched individually.
3. Confirm job identity, descriptions, cache population, and Rules Engine behavior.
4. Confirm candidate indexing behaves correctly when no resume is available.
5. Upload an interview PDF and result link to a dummy application and confirm both are recruiter-visible in ADP.
6. Record unsupported checklist rows as accepted exceptions before go-live.

## References

* [Kombo ADP Workforce Now connector](https://docs.kombo.dev/ats/connectors/adpworkforcenow)
* [ATS integration checklist](/internal/ats-implementation-notes)