# CATS integrations: candidates, jobs and pipelines

> Create a candidate, create a job and create a pipeline in CATS, and start a workflow when CATS sends “Candidate created”.

**Canonical page:** https://tray.ai/connectors/cats-integrations/
**Categories:** Human resources
**Connects through:** HTTP Connector

## Overview

CATS is an applicant tracking system for recruiters and staffing agencies that tracks candidates, jobs, client companies, contacts, and hiring pipelines. Tray.ai connects to CATS through the HTTP Connector, so your workflows can call the CATS API alongside the rest of your stack.

## Use cases

### Candidates

Read, create, and delete candidates in CATS from any Tray.ai workflow. The CATS API covers calls such as filter candidates and get a candidate.

- Filter candidates
- Get a candidate
- Create a candidate

### Jobs

Read, create, update, and delete jobs in CATS from any Tray.ai workflow. The CATS API covers calls such as filter jobs and get a job.

- Filter jobs
- Get a job
- Create a job

### Pipelines

Read, create, update, and delete pipelines in CATS from any Tray.ai workflow. The CATS API covers calls such as filter pipelines and get a pipeline.

- Filter pipelines
- Get a pipeline
- Create a pipeline

### Companies

Read, create, and delete companies in CATS from any Tray.ai workflow. The CATS API covers calls such as filter companies and get a company.

- Filter companies
- Get a company
- Create a company

### Contacts

Read, create, and delete contacts in CATS from any Tray.ai workflow. The CATS API covers calls such as filter contacts and get a contact.

- Filter contacts
- Get a contact
- Create a contact

### Tasks

Read, create, and delete tasks in CATS from any Tray.ai workflow. The CATS API covers calls such as get a task and create a task.

- Get a task
- Create a task
- Delete a task

## Challenges Tray.ai solves

### Keeping CATS credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store CATS credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the CATS API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the CATS API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to CATS?

Yes. Tray.ai connects to CATS through the HTTP Connector, which calls the CATS API directly. Any call the CATS API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with CATS?

The CATS API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated CATS connector?

CATS runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated CATS connector from the CATS API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/