Skip to main content

​
Implementation overview

Implementation type: Kombo-based integration Status: In development Loxo connects through Kombo’s unified ATS API. The integration reuses the shared Kombo paths for reading and writing jobs, applications, candidates, and application stages. Anything Kombo’s Loxo connector does not cover goes through Kombo passthrough (loxo/v1) to Loxo’s own API. Job custom-field writes are not enabled yet.

​
Reads

  • 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 job custom-field values from the normalized Kombo job, with no extra request.
  • 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 loxo connection.
All sync flags remain disabled when the integration is first created. They must be enabled deliberately after the connected tenant is ready for validation.

​
Writes

  • Move applications to the configured stage targets through Kombo.
  • Handle rejection outcomes (fail, thumbs-down, not interested, timeout) as stage moves to a configured stage, such as Loxo’s “Rejected” stage. Disposition reasons are not used.
  • Post notes on applications through Kombo: interview results, SMS and email activity, and stage transitions.
  • Post notes on candidates (for example, sourced candidates with no application) as an “Interview Note” activity on the Loxo person, with no job attached. Loxo stage triggers apply to job pipelines, so these notes do not move the candidate. The activity type is looked up by its interview_note key in each agency.
  • Upload the interview results PDF through Kombo. Loxo may store it on the candidate instead of the application.
  • Write the interview score and the interview link to the selected candidate custom fields through Loxo’s person update API. Loxo has no application custom fields, so both are stored on the candidate. A candidate interviewed for several jobs keeps only the latest score and link.

​
Known connector limitations

Kombo documents these Loxo actions: create candidate, create application, move application to stage, add note to application, add attachment to candidate or application, and get candidate attachments.
  • Creating a candidate or an application requires a phone number and a CV. Tenzo creates applications through Kombo with the candidate’s first phone number and their Loxo resume attached as the CV. When either is missing, Tenzo skips the application and logs why; no note is posted.
  • Tenzo does not create Loxo candidates. Applications are created only for candidates who already exist in Loxo; a sourced candidate with no Loxo record is skipped.
  • Stage moves are forward-only. A stage target that sits before the application’s current stage is refused, so pick targets later in the Loxo pipeline.
  • An application attachment may land on the candidate instead.
  • Kombo documents no rejection or disposition action, no candidate notes, and no custom-field writes for Loxo. Candidate notes and candidate custom fields use Loxo’s own API through passthrough.
  • The candidate custom-field selectors list the agency’s own Loxo person fields (text and number fields the agency created), not Kombo’s mapped fields. Create a text field for the score and one for the interview link in Loxo before selecting them.

​
Configuration

The configuration exposes:
  • Start Stages as the inbound eligibility filter (which applicants Tenzo picks up)
  • Stage targets for resume review, AI interview, human review, accommodation, cooling down, outreach, call limits, stage routing rules, and contact or consent problems
  • Stage targets for thumbs-up, thumbs-down, not interested, and interview timeout
  • AI interview scoring thresholds
  • Interview results note and PDF, SMS and email activity notes, and stage-transition notes
  • Candidate custom fields for the interview score and the interview link
  • When to create an ATS application for a sourced candidate who already exists in Loxo
  • Automatic job activation and activation delay
  • Syncing applicants for paused jobs
The job link and application score selectors are not exposed.

​
Validation required before enablement

  1. Connect a Loxo tenant through Kombo and add its ATS integration record.
  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 which Loxo job statuses count as open, and which field is the recruiter title vs the posting title.
  5. Confirm the application-stage catalog loads, and pick the Start Stages.
  6. Record unsupported checklist rows as accepted exceptions before go-live.

​
References