# Ashby AI integration on Definable

> Ashby delivers an applicant tracking system for modern teams, offering features like job postings, candidate management, and data-driven hiring insights to streamline the recruitment process

## What this connects

Ashby delivers an applicant tracking system for modern teams, offering features like job postings, candidate management, and data-driven hiring insights to streamline the recruitment process

Vendor: https://www.ashbyhq.com

## Tools available

**125** tools available. First 12:

- `ASHBY_ADD_CANDIDATE_PROJECT` — Add Candidate to Project — Add a candidate to a project in Ashby. Projects are sourcing initiatives or recruiting campaigns used to organize and track candidate pipelines. Use this to associate candidates with specific sourcing efforts. Common use cases: - Adding sourced candidates to recruiting campaigns - Organizing candidates by sourcing channel or initiative - Tracking candidates in specific hiring projects Requires candidatesWrite permission. Returns the updated candidate object on success, or error details if the candidate or project is not found.
- `ASHBY_ADD_CANDIDATE_TAG` — Add Candidate Tag — Add a tag to a candidate in Ashby. Use this to categorize and organize candidates with existing tags from the system. This action allows you to apply labels/tags to candidates for filtering, searching, and organizational purposes. Tags must already exist in the system - use LIST_CANDIDATE_TAGS to view available tags or CREATE_CANDIDATE_TAG to create new ones. The response includes the full updated candidate object when successful, showing the newly added tag in the candidate's tags array. If a candidate already has the tag, the operation will still succeed idempotently.
- `ASHBY_ADD_HIRING_TEAM_MEMBER` — Add Hiring Team Member — Add an Ashby user to a hiring team at the application, job, or opening level. Use this when you need to assign a team member to participate in the hiring process with a specific role. Requires the organizationWrite permission.
- `ASHBY_ADD_INTERVIEWER_POOL_USER` — Add User to Interviewer Pool — Add a user to an interviewer pool. Use this to assign interviewers to interview pools for scheduling and coordination. Requires the hiringProcessMetadataWrite permission.
- `ASHBY_ADD_OPENING_JOB` — Add Opening Job — Adds a job to an opening (job requisition) in Ashby ATS. An opening represents a position to be filled, while a job defines the role details. This action associates an existing job with an existing opening, allowing multiple jobs to be linked to a single opening. Use this when you need to add job definitions to an opening or when creating multi-role requisitions. Requires the jobsWrite permission. On success, returns the updated opening with the job added to its jobIds array. On failure, returns error details with specific error codes.
- `ASHBY_ADD_OPENING_LOCATION` — Add Opening Location — Tool to add a location to an opening (job requisition). Use when you need to associate a location with an existing opening. Requires the jobsWrite permission.
- `ASHBY_ANONYMIZE_CANDIDATE` — Anonymize Candidate — Anonymize a candidate by removing personally identifiable information. Use this when you need to permanently anonymize a candidate's data. This action cannot be reversed and requires all of the candidate's applications to be in the archived or hired state.
- `ASHBY_APPROVE_OFFER` — Approve Offer — Approve an offer or a specific approval step within an offer's approval process. This action supports two modes: - Complete offer approval: Provide only offerId to approve the entire offer - Step-specific approval: Provide offerId, approvalStepId, and userId to approve a specific step When approving a specific step, both approvalStepId and userId are required together. Requires the 'offersWrite' permission.
- `ASHBY_ARCHIVE_DEPARTMENT` — Archive Department — Archive a department by its unique identifier. Archiving a department marks it as inactive while preserving all its data and historical records. Archived departments are excluded from active department lists by default but can be restored later using the restore department action. This action is idempotent - archiving an already archived department will succeed and return the same result. Required permission: organizationWrite
- `ASHBY_ARCHIVE_INTERVIEWER_POOL` — Archive Interviewer Pool — Archive an interviewer pool in Ashby. This marks the pool as archived, making it unavailable for new interview assignments while preserving historical data. Use this when an interviewer pool is no longer needed (e.g., for deprecated roles or outdated interview formats). The operation is idempotent - archiving an already archived pool will succeed without errors. Requires the hiringProcessMetadataWrite permission. To restore an archived pool, use the ASHBY_RESTORE_INTERVIEWER_POOL action.
- `ASHBY_ARCHIVE_LOCATION` — Archive Location — Archives a location or location hierarchy in Ashby. When archived, the location is marked as inactive (isArchived=true) and typically becomes unavailable for new job postings or assignments. The operation is idempotent - archiving an already archived location succeeds without error. Requires the organizationWrite permission. Common use cases: - Decommissioning office locations that are no longer in use - Removing obsolete location entries from active use - Managing location lifecycle when restructuring office locations Note: Use restore_location to unarchive a location if needed.
- `ASHBY_CHANGE_APPLICATION_SOURCE` — Change Application Source — Change the source attribution of an application. Use this to update which source and user should be credited for bringing in the candidate.

## Auth

Auth schemes: `API_KEY`.

## How agents use Ashby

Inside a Definable workflow, Ashby is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Ashby** — the Researcher (GPT-5.5) pulls context from Ashby (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Ashby** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Ashby (create record, post message, draft email).
- **Designer / Engineer → Distributor → Ashby** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Ashby (attach file, open PR comment, post status).

The Verifier checks every Ashby call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- hr talent & recruitment — https://definable.ai/apps/category/hr-talent-&-recruitment/

## Related

- HTML page: https://definable.ai/apps/ashby/
- Same category (hr talent & recruitment): https://definable.ai/apps/category/hr-talent-&-recruitment/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt