# Ashby integrations: candidates and applications

> Create a candidate, create an application and create a job in Ashby, and start a workflow when Ashby sends “Application submitted”.

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

## Overview

Ashby is a recruiting platform that tracks candidates, applications, jobs, interviews, and offers in one hiring system with built-in scheduling and analytics. Tray.ai connects to Ashby through the HTTP Connector, so your workflows can call the Ashby API alongside the rest of your stack.

## Use cases

### Candidates

Read, create, and update candidates in Ashby from any Tray.ai workflow. The Ashby API covers calls such as list candidates and create a candidate.

- List candidates
- Create a candidate
- Update a candidate

### Applications

Read, create, and update applications in Ashby from any Tray.ai workflow. The Ashby API covers calls such as list applications and create an application.

- List applications
- Create an application
- Change an application stage

### Jobs

Read, create, and update jobs in Ashby from any Tray.ai workflow. The Ashby API covers calls such as list jobs and create a job.

- List jobs
- Create a job
- Update a job

### Interview schedules

Read, create, update, and delete interview schedules in Ashby from any Tray.ai workflow. The Ashby API covers calls such as list interview schedules and create an interview schedule.

- List interview schedules
- Create an interview schedule
- Update an interview schedule

### Offers

Read, create, and update offers in Ashby from any Tray.ai workflow. The Ashby API covers calls such as list offers and create an offer.

- List offers
- Create an offer
- Update an offer

### Ashby events

Start a Tray.ai workflow the moment something happens in Ashby. Ashby sends events such as application submitted and application updated to a Tray.ai webhook trigger.

- Application submitted
- Application updated
- Candidate hired

## Challenges Tray.ai solves

### Keeping Ashby 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 Ashby 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 Ashby 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 Ashby 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 Ashby?

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

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

The Ashby API uses basic authentication. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Ashby connector?

Ashby runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Ashby connector from the Ashby 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/