# Ashby integration overview

> Pull Ashby candidate and application data into Persona, update candidate profiles, and trigger workflows from Ashby webhooks.

Source: https://help.withpersona.com/articles/4424mgQ8LTAJaUBdeESoRv/
Section: Marketplace and 3rd-Party Integrations > ATS > Ashby

## Overview

[Ashby](https://www.ashbyhq.com/) is an all-in-one recruiting platform (ATS, sourcing, scheduling, CRM, and analytics) that helps teams streamline hiring. Persona’s Ashby integration brings candidate and application context into your identity workflows and lets you take action without switching tools.

With this integration, you can enrich Persona with Ashby candidate/application data, keep profiles up to date, and trigger downstream steps (like sending an inquiry link) when interviews are scheduled or offers change, helping Recruiting and Talent teams work faster with full context.

## Benefits

**Automated Recruiting Ops**: Kick off workflows from interview or offer events so teams don’t need to babysit updates across systems.

**Real-Time Insight**: Pull fresh candidate and application details to inform decisions inside Persona.

**Candidate Fraud Mitigation**: Use timely events (e.g., interview scheduled) to send the right outreach or verification at the right time.

## Integration Features

Persona’s Ashby integration supports bi-directional flows, bringing data into Persona and updating records in Ashby. Key capabilities include:

- **Retrieve Candidate Information**: Pull information on candidates and their applications directly from Ashby. Keep candidate profiles current by updating names, emails, phone numbers, social links, location, and more.
- **Automate Workflow Actions:** React to interview, offer, stage-change, and new-application webhooks to trigger automations as recruiting milestones change.

## Setting up the Ashby integration

### Prerequisites

To set up the Ashby integration, ensure you have:

- Admin access to your Ashby account
- Necessary API permissions to access Ashby credentials

### Setting up the Ashby Credentials

1.  In the Persona Dashboard, go to **Integrations > Marketplace** and select **Ashby**.
2.  Click **Add Credential** at the top of the page.
3.  Enter a credential nickname and click **Continue**.
4.  In Ashby, go to **Admin > Integrations > API Keys**, and click **\+ New**
    - Provide a name for the API key. Click **Create API Key**
    - For API Scopes, select Candidates Read and Write. Click **Save and Continue**
    - Copy your API key.
5.  Paste your API key into Persona to finish connecting. You can test or remove the credential at any time.

### Configuring Webhooks

1.  In Persona, open the Ashby integration page and click **Add webhook**.
2.  Select the Persona environment(s) the webhook will be active in, then set a signature key (save this, you’ll reuse it in Ashby).
    - The signature key will be used to cryptographically sign all webhook payloads and ensure the information is transmitted securely from Ashby to Persona.
    - The signature key can be any value, but it is recommended that the key is a long, random, and complex string, such as `a7e4a56cf7c1cd80cb1c735c72bab2aa75d06fe08b8c50a18cf6afbcfe834122`.
3.  In Ashby, go to **Admin > Webhooks** and click **\+ New**.
4.  Choose the event you want to send to Persona. Persona supports receiving four types of webhook updates:
    - **Interview schedule updated**: Get notified when an interview schedule is created, updated, or canceled, including interview times, interviewers, and related schedule details. Trigger steps like sending an inquiry link before interviews or updating internal case context.
    - **Offer updated**: Receive an event whenever an offer is updated, such as changes to offer status, acceptance status, start date, salary, or custom fields.
    - **Candidate application stage change**: Get notified when a candidate changes stage, like moving from the recruiter phone screening stage to the hiring manager interview stage.
    - **Application submitted**: Get notified when a candidate submits an application or is manually added to Ashby. Use the submission context from the payload, such as the submitter's IP address, to kick off fraud checks or verification workflows.
5.  Paste the Persona webhook URL and enter the same signature key from step 2. Save your webhook.

ℹ️

Because webhooks are used as a way to trigger Persona workflows, each environment you select for a webhook will cause a workflow run in that environment when the webhook fires.

### Using the Ashby integration in a workflow

1.  Create a new workflow, or open an existing one.
2.  Add an Action step and choose Integrations.
3.  Select the Ashby integration and your saved credentials.
4.  Choose the operation (e.g., Retrieve Application, Retrieve Candidate, Update Candidate) and map Persona data to Ashby fields (and vice versa) as needed.
5.  Save and publish the workflow.

Tip: When reacting to an Offer updated event, first retrieve the application from the webhook payload to access the candidate ID, then Retrieve Candidate and continue with actions like sending an inquiry link email.

## Ashby Operations Overview

In addition to syncing field values, Persona can retrieve and update candidate profiles, retrieve applications, read location details, manage files, and list data using Ashby's API. These actions support seamless two-way workflows, letting teams manage investigations without switching platforms.

See below for a comprehensive list of available Workflow Action steps and possible configurations for the Ashby integration:

### Retrieve Candidate

Pull detailed information about a specific candidate to enrich Persona with contact info, social links, tags, resume/file references, and associated applications. This is useful for building context before outreach, verification, or adjudication steps.

Configuration Steps:

- Provide values for required fields:
  - Candidate ID

### Update Candidate

Update an existing candidate’s profile so records stay current as you progress through reviews or investigations. You can update name, emails, phone numbers, social links (e.g., LinkedIn), location, credited user/source, and more, and optionally notify stakeholders of the change.

Configuration Steps:

- Provide values for required fields:
  - Candidate ID
- Optionally add:
  - Name
  - Email and/or alternate email
  - Phone number
  - Social links (e.g., LinkedIn, GitHub, website)
  - Location (city/region/country)
  - Source ID and/or credited user ID
  - Send notifications (toggle)

### Retrieve Application

Fetch a specific application’s status, current stage, job details, history, hiring team, and related candidate context. This helps determine next actions (e.g., send verification upon stage change) and ensures downstream steps use the latest information.

Configuration Steps:

- Provide values for required fields:
  - Application ID

### Set a Custom Field

Update the custom field of an object, such as an Application, Candidate, Job, or Opening. Use this to pass information from Persona into Ashby, like verification status of a candidate.

Configuration Steps:

- Provide values for required fields:
  - Object ID
  - Object Type
  - Field ID
    - Note: obtain this using the List Custom Fields operation
  - Field Value
    - Note: for this integration, only a `string` field value type is accepted.

### Retrieve Location

Fetch the details of a single Ashby location by ID, including name, address, workplace type, and whether it is remote. This is useful when a candidate's application references a location you want to confirm before outreach, verification, or adjudication.

Configuration Steps:

- Provide values for required fields:
  - Location ID

### File Operations

Upload and retrieve files attached to a candidate's profile:

- **Create Upload Handle**: Get a presigned upload URL and a file handle for a new file, ready to attach to a candidate.
- **Upload File to Candidate**: Attach an uploaded file to a specific candidate's profile using the file handle.
- **Retrieve File Info**: Get the URL of a file associated with a candidate using its file handle.

Configuration Steps for **Upload File to Candidate**:

- Provide values for required fields:
  - Candidate ID
  - File Handle

Configuration Steps for **Create Upload Handle**:

- Provide values for required fields:
  - Filename
  - Content Type
  - Content Length

Configuration Steps for **Retrieve File Info**:

- Provide values for required fields:
  - File Handle

### Listing Endpoints

These endpoints let Persona fetch metadata to build dynamic workflows:

- **List Candidates**: retrieve candidate records with pagination and incremental sync tokens.
- **List Custom Fields**: retrieve custom field definitions with pagination (using cursors) and optional incremental sync (using sync tokens).

## FAQs

### What permissions are required in Ashby?

You’ll need sufficient permissions to create and manage API keys and to access candidates and applications. Your Ashby admin can confirm the exact privileges for your organization.

### Can I connect a sandbox or test environment?

Yes. Create an API key in the Ashby environment you wish to use (e.g., test/sandbox) and add it as a separate credential in Persona.

### Which webhook events are supported?

Persona supports four Ashby webhook events: Application submitted, Candidate application stage changed, Offer updated, and Interview schedule updated. Use these to trigger time-sensitive workflows like sending inquiry links or updating case status based on recruiting milestones.

## Plans Explained

### Ashby Integration by plan

|                   | Startup Program | Essential Plan | Growth Plan | Enterprise Plan |
| ----------------- | --------------- | -------------- | ----------- | --------------- |
| Ashby Integration | Not Available   | Not Available  | Limited     | Available       |

[Learn more about pricing and plans](https://withpersona.com/pricing?utm_source=product&utm_medium=referral&utm_audience=a&utm_campaign=cm_gen_ds_hc-plan-table).

_Last updated on August 20, 2026._