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

# Ashby Integration

> Import job applicants from Ashby into Sixtyfour workflows to research and rank them.

Connect Ashby to Sixtyfour to import job applicants into a workflow, then research, score, and export them. Sixtyfour only reads from Ashby. It never changes or writes back to your Ashby data.

> [!NOTE]
>
> The Ashby integration is in early access. Contact [support@sixtyfour.ai](mailto:support@sixtyfour.ai) to turn it on for your organization.

## What Sixtyfour reads

The API key created from the Sixty Four tile in Ashby has read access to two Ashby modules.

| Ashby module | What Sixtyfour reads |
| - | - |
| Jobs | Open jobs, their titles, and job posting descriptions |
| Candidates | Applications (status, interview stage, applied date, source), candidate profiles (name, email, phone, social links, current title, company, school, location), and résumé files |

Sixtyfour reads Ashby only when you connect a key, pick jobs in the Import Data block, or run a workflow.

## Create an API key in Ashby

You need Admin access in Ashby to create the key.

**1. Open Admin**

Sign in to [Ashby](https://app.ashbyhq.com) and click **Admin** in the top navigation bar.

![Ashby top navigation bar with Admin highlighted](https://mintcdn.com/sixtyfour/nb2qh5icG8Oz3-RM/images/ashby-admin-nav.png?fit=max\&auto=format\&n=nb2qh5icG8Oz3-RM\&q=85\&s=1a88594c4df1f7cb7f3027b14818fcc5)

**2. Open Integrations**

In the left panel, open **Integrations** and click **Integrations**.

![Ashby Admin Integrations page with the Integrations item highlighted in the left panel](https://mintcdn.com/sixtyfour/nb2qh5icG8Oz3-RM/images/ashby-integrations-page.png?fit=max\&auto=format\&n=nb2qh5icG8Oz3-RM\&q=85\&s=c3b0f5183741c4e4c7426fbd5e2a2893)

**3. Open the Sixty Four tile**

Search for **Sixty Four** and select the tile.

![Ashby Integrations page filtered to the Sixty Four tile](https://mintcdn.com/sixtyfour/nb2qh5icG8Oz3-RM/images/ashby-sixtyfour-tile.png?fit=max\&auto=format\&n=nb2qh5icG8Oz3-RM\&q=85\&s=fe95f35702fa2e2a8bb07cfb2217a558)

**4. Create and copy the key**

Click **Create API key for Sixty Four** and copy the key Ashby shows. You paste it into Sixtyfour in the next section.

![Sixty Four panel in Ashby with the Create API key for Sixty Four button highlighted](https://mintcdn.com/sixtyfour/nb2qh5icG8Oz3-RM/images/ashby-create-api-key.png?fit=max\&auto=format\&n=nb2qh5icG8Oz3-RM\&q=85\&s=b28179641b16b508d36ae2bf1294dee0)

## Connect the key in Sixtyfour

**1. Open the Ashby integration**

In the [Sixtyfour dashboard](https://app.sixtyfour.ai), go to **Settings → Integrations** and select **Ashby**.

![Sixtyfour Integrations settings page showing the Ashby card](https://mintcdn.com/sixtyfour/nb2qh5icG8Oz3-RM/images/ashby-sixtyfour-integrations.png?fit=max\&auto=format\&n=nb2qh5icG8Oz3-RM\&q=85\&s=ceba8e02a313004a55613f49741d042d)

**2. Paste the key and connect**

Paste the key into **API key** and click **Connect**. Sixtyfour checks that the key can read jobs and candidates before saving it.

![Ashby settings page in Sixtyfour with the API key field and Connect button highlighted](https://mintcdn.com/sixtyfour/nb2qh5icG8Oz3-RM/images/ashby-sixtyfour-connect.png?fit=max\&auto=format\&n=nb2qh5icG8Oz3-RM\&q=85\&s=0f1d027d4fa06b7c8169ba6844dcb947)

The connection belongs to your current team. Every workflow in the team that imports from Ashby uses it. Sixtyfour encrypts the key with your organization's own encryption key.

## Import applicants into a workflow

**1. Add an Import Data block**

Open the [Workflow Editor](https://app.sixtyfour.ai/workflows), add an **Import Data** block, and set **Import from** to **Ashby · Job applicants**.

![Import Data block configured to import Ashby job applicants](https://mintcdn.com/sixtyfour/nb2qh5icG8Oz3-RM/images/ashby-import-data-block.png?fit=max\&auto=format\&n=nb2qh5icG8Oz3-RM\&q=85\&s=124db1f19e9050a595be3c6789681456)

**2. Choose which applicants to import**

| Setting | What it does |
| - | - |
| Jobs | The open jobs to import applicants from. Leave all unchecked to import from every open job. |
| Application status | Active, Lead, Hired, or Archived. Defaults to Active. |
| Interview stages | Comma-separated stage names, such as `Application Review, Recruiter Screen`. Leave empty for every stage. |
| Applied in the last (days) | Only applicants who applied in this many days. Leave empty for any time. |
| Add job description | Adds the job posting's description as `job_description`. |
| Read résumés | Adds the text of each résumé PDF as `resume_text`. |
| Maximum rows | Caps how many applicants the run imports. |

**3. Add Intelligence and output blocks**

Each applicant becomes one row, so any people block can follow. A common pattern researches applicants and sends the results to your own system:

```mermaid theme={null}
flowchart LR
  Ashby[Import Data: Ashby] --> Enrich_People[Enrich People] --> Webhook[Outgoing Webhooks]
```

**4. Run the workflow**

Run the workflow from the editor, or put it on a [schedule](https://docs.sixtyfour.ai/guides/automated-workflows.md) to pick up new applicants as they apply.

### Imported columns

| Column | Description |
| - | - |
| `name`, `email`, `phone` | From the candidate's Ashby profile |
| `linkedin`, `github`, `website` | The candidate's social links in Ashby |
| `title`, `company`, `school`, `location` | The candidate's current role and background in Ashby |
| `job_title` | The job the candidate applied to |
| `application_status`, `interview_stage` | Where the application stands |
| `applied_at`, `source` | When and how the candidate applied |
| `ashby_application_id`, `ashby_candidate_id`, `ashby_job_id` | Ashby IDs, for matching results back to Ashby |
| `ashby_profile_url` | Link to the candidate in Ashby |
| `job_description` | Present when **Add job description** is on |
| `resume_text` | Present when **Read résumés** is on |

## Disconnect Ashby

* In Sixtyfour, go to **Settings → Integrations → Ashby**, click the trash icon next to the key, and confirm **Disconnect**.
* In Ashby, deactivate the key under **Admin → API Credentials**.

> [!WARNING]
>
> Workflows that import from Ashby stop until the team connects a key again.

## Troubleshooting

| Message | Fix |
| - | - |
| Ashby rejected this team's connection | The key was deactivated in Ashby. Create a new key from the Sixty Four tile and use **Replace key** in Sixtyfour. |
| The Ashby key can't read Jobs and Candidates | The key is missing a permission. Create the key from the Sixty Four tile, which grants the permissions Sixtyfour needs. |
| The run imports no applicants | Check **Application status** and **Applied in the last (days)**. Only open jobs appear in the job list. |

## Block reference

| Field | Value |
| - | - |
| Block type | `read_csv` with `specs.source.type` set to `ashby_applicants` |
| Pipeline position | Source (first block) |
| Requires integration | Yes, the team must have Ashby connected |
| Output data type | Lead |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.