Ashby for AI agents
Agents read Ashby at once. Changes and sends are held for a person's approval by default.
About Ashby
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 an agent can do in Ashby
Every Ashby action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Ashby without asking first. 63 actions.
- Get API Key InfoRetrieve information about the current API key, including associated organization, user details, and permissions. Use this to verify API key validity and check what access level the key has. Useful as
- Get Application InfoRetrieve detailed information about a specific application by its ID. Returns complete details including candidate info, interview stages, and hiring team nested under data.results. To find a recruiti
- Get Candidate InfoRetrieve detailed information about a specific candidate by their ID. This action returns comprehensive candidate data including: - Basic information (name, position, company, school) - Contact detail
- Get File InfoRetrieve the URL of a file associated with a candidate. Use this to get a pre-signed S3 URL for accessing candidate files like resumes. Requires the candidatesRead permission.
- Get Job InfoRetrieve detailed information about a specific job by its ID. Use this to get complete details about a job including title, status, hiring team, interview plans, and more. Job offer payloads omit full
- Get Job Interview Plan InfoRetrieve the interview plan information for a specific job. Use this to get details about the interview stages and process configured for a job.
- Get Job Posting InfoRetrieve detailed information about a specific job posting by its ID. Use this to get complete job posting details including full description, application form fields, compensation, and publish settin
- Get Offer InfoRetrieve detailed information about a specific offer by its ID. This action returns comprehensive offer data including application ID, status, version, timestamps, candidate ID, job ID, start date, an
- Get Opening InfoRetrieve detailed information about a specific opening (job requisition) by its ID. An opening represents a headcount position that needs to be filled. Each opening belongs to a job and tracks hiring
- Get User InfoRetrieve detailed information about a specific user by their ID. Use this to get user details including name, email, role, and permissions.
- List ApplicationsRetrieve a list of applications with optional pagination and sync-token filtering for incremental updates. No server-side recruiter filter exists; attribute applications to team members client-side.
- List CandidatesRetrieve a list of candidates. Use this to fetch all candidates with optional pagination and filtering by sync token for incremental updates.
Show all 63
- List Custom FieldsRetrieve a list of all custom field definitions configured in Ashby. Use this action to discover what custom fields are available for candidates, applications, jobs, offers, and openings. This is usef
- List DepartmentsRetrieve a list of all departments in the organization. Use this action to: - Get all departments for organizing jobs and candidates by team structure - Find department IDs needed for creating or filt
- List Interview PlansRetrieve a list of interview plans. Use this to get the structured interview processes and stages configured for different roles.
- List Interview TypesList all interview types defined in Ashby. Returns interview templates/definitions (e.g., 'Technical Phone Screen', 'Debrief', 'Intro Call with CEO') rather than scheduled interview instances. Use thi
- List Interview SchedulesRetrieve a list of interview schedules. Use this to fetch all scheduled interviews with candidates, including timing, interviewers, and interview details.
- List Job PostingsRetrieve a list of job postings. Use this to fetch all public job postings with optional pagination and filtering. May return zero results even when open jobs exist; if so, use ASHBY_LIST_JOBS as a fa
- List JobsRetrieve a list of all jobs from Ashby ATS (Applicant Tracking System). Use this action to: - Fetch all open, closed, or draft jobs in your organization - Get job details including title, status, empl
- List LocationsRetrieve a list of all locations. Use this to get available office locations and remote work settings for jobs.
- List OffersRetrieve a list of job offers with their latest versions. This action fetches all offers made to candidates in your Ashby account. Use pagination (cursor/perPage) to handle large result sets efficient
- List OpeningsRetrieve a list of openings (job requisitions). Use this to fetch all openings with optional pagination and filtering. Each opening may represent multiple hires; inspect headcount fields rather than a
- List SourcesRetrieve a list of all candidate sources. Use this to get available sources for categorizing how candidates were sourced (e.g., LinkedIn, referrals, job boards).
- List UsersRetrieve a list of all users in the organization. Use this to get information about team members, their roles, and permissions.
- Search CandidatesSearch for candidates by email or name. Use this for quick lookups to find specific candidates without pagination. Supports exact email match or partial name match.
- Search JobsSearch for jobs by title in Ashby ATS (Applicant Tracking System). Use this action to: - Quickly find jobs by title without pagination - Perform partial match searches (e.g., "engineer" matches "Backe
- Search OpeningSearch for openings by identifier. Use this for quick lookups to find specific openings without pagination. Returns empty results if no match found.
- Get Custom Field InfoRetrieve detailed information about a specific custom field by its ID. Use this to get custom field details including title, object type, field type, and selectable values. Requires the hiringProcessM
- Get Department InfoRetrieve detailed information about a specific department by its ID. Returns comprehensive department details including: - Department name (internal and external) - Parent department relationship (par
- Get Feedback Form DefinitionRetrieve detailed information about a specific feedback form definition by its ID. Use this action to: - Get the complete structure of a feedback form including all sections and fields - View field ty
- Get Interviewer Pool InfoRetrieve detailed information about a specific interviewer pool by its ID. Returns comprehensive pool information including: - Basic details (ID, title, archived status) - Qualified members who can co
- Get Interviewer User SettingsGet interviewer settings for a specific user by their ID. Use this to retrieve daily and weekly interview limits configured for the user. Requires the organizationRead permission.
- Get Interview InfoRetrieve detailed information about a specific interview type by its ID. Use this to get interview details including title, instructions, and feedback form configuration.
- Get Interview Stage InfoTool to fetch interview stage details by ID. Use when you need specific information about an interview stage including its title, type, order, and parent interview plan. Requires the interviewsRead pe
- Get Location InfoRetrieve detailed information about a specific location by its ID. Use this to get complete location details including address, remote status, and workplace type.
- Get Survey Form DefinitionRetrieve detailed information about a specific survey form definition by its ID. This action returns comprehensive details about a survey form including: - Survey title and type (e.g., Diversity, EEOC
- List Application Criteria EvaluationsRetrieve AI-generated criteria evaluations for an application. Use this to get the AI assessment of how well a candidate meets specific job requirements, including evaluation outcomes and reasoning.
- List Application FeedbackRetrieve all feedback submissions for an application. Use this to view interviewer feedback, evaluations, and notes collected throughout the hiring process.
- List Application Hiring Team RolesRetrieve all available hiring team roles for applications in the organization. These roles can be assigned to hiring team members at the application level (e.g., Recruiter, Hiring Manager, Recruiting
- List Application HistoryRetrieve the complete history of stage transitions for an application. Use this to get detailed information about when and how a candidate moved through different interview stages.
- List ApprovalsRetrieve a list of approvals (offer approvals, job approvals, etc.). Use this to track approval workflows and pending approvals.
- List Archive ReasonsRetrieve a list of all archive reasons. Use this to see available reasons for archiving candidates or applications, such as rejection categories.
- List BrandsRetrieve a list of all brands for the organization. Use this to get available brands for job postings and employer branding. Requires organizationRead permission.
- List Candidate Client InfoRetrieve all client info records for a specific candidate with pagination support. Client info records contain additional client-specific information associated with candidates in your Ashby account.
- List Candidate NotesRetrieve all notes for a specific candidate in Ashby. Use this action to view comments, observations, and internal notes added by recruiters and hiring team members during the hiring process. Common u
- List Candidate ProjectsRetrieve all projects associated with a candidate. Use this to see which sourcing projects or recruiting initiatives a candidate is part of.
- List Candidate TagsRetrieve a list of all candidate tags in your Ashby account. Tags are labels used to categorize and organize candidates for filtering and search purposes. Use this action to: - Get all available tags
- List Close ReasonsLists all close reasons for jobs or openings. Close reasons categorize why a job or opening was closed (e.g., rejected by candidate, rejected by organization, or other reasons). Requires hiringProcess
- List Communication TemplatesRetrieve a list of all communication templates. Use this to see available email and message templates for candidate outreach.
- List Feedback Form DefinitionsRetrieve all feedback form definitions from your Ashby organization. Use this action to: - Discover available interview feedback templates - Get form IDs for use with other feedback-related actions -
- List Hiring Team RolesRetrieve a list of possible hiring team roles in the organization. Use this to get available roles that can be assigned to members of a hiring team (e.g., Hiring Manager, Recruiter, Recruiting Coordin
- List Interviewer PoolsRetrieve a list of all interviewer pools. Interviewer pools are groups of interviewers organized by expertise, role, or interview type (e.g., "Backend Engineer", "Bar Raiser"). Use this to see availab
- List Interview EventsRetrieves all interview events for a specific interview schedule. Each interview event represents a scheduled time slot with assigned interviewers for conducting interviews. Use this action to: - Get
- List Interview Stage GroupsRetrieve a list of interview stage groups. Use this to see how interview stages are organized into logical groups within interview plans.
- List Interview StagesRetrieve all interview stages for an interview plan in order. Use this to get the structured sequence of stages a candidate progresses through during the interview process for a specific role. Require
- List Job BoardsRetrieve a list of job boards. Use this to see where job postings can be published (e.g., LinkedIn, Indeed, company career page).
- List Job TemplatesRetrieve a list of all job templates from Ashby ATS. Use this action to: - Discover available job templates for creating standardized job postings - View both active and inactive templates in your org
- List ProjectsRetrieve a list of all projects. Use this to see candidate sourcing projects and recruiting initiatives.
- List Source Tracking LinksRetrieve all source tracking links configured in Ashby. Source tracking links are UTM-tagged URLs used to track where candidates are coming from (e.g., LinkedIn, job boards, referral campaigns). Use t
- List Survey Form DefinitionsRetrieve a list of all survey form definitions from Ashby. Use this action to discover available candidate survey templates including: - Candidate Experience Surveys (NPS ratings for candidate feedbac
- List Survey SubmissionsLists all survey submissions of a given survey type from Ashby. Survey submissions contain candidate responses to surveys sent during the hiring process. Use this action to: - Retrieve candidate exper
- Search ProjectsSearch for projects by title in Ashby. Projects in Ashby are used to track sourcing initiatives, recruiting campaigns, or candidate portfolios. Use this action to: - Quickly find projects by title wit
- Search UsersSearch for an Ashby user by email address. Use this to find specific team members in the organization when you know their email. Returns matching user details including their ID, name, role, and statu
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 62 actions.
- Add Candidate to ProjectAdd 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
- Add Candidate TagAdd 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
- Add Hiring Team MemberAdd 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 org
- Add User to Interviewer PoolAdd a user to an interviewer pool. Use this to assign interviewers to interview pools for scheduling and coordination. Requires the hiringProcessMetadataWrite permission.
- Add Opening JobAdds 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 op
- Add Opening LocationTool 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.
- Approve OfferApprove 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-spec
- Change Application SourceChange the source attribution of an application. Use this to update which source and user should be credited for bringing in the candidate.
- Change Application StageMove an application to a different interview stage in the hiring pipeline. Use this to: - Advance candidates to the next interview stage (e.g., from "Application Review" to "First Round") - Move candi
- Create ApplicationCreate a new job application by associating a candidate with a job opening in Ashby ATS. Use this action to: - Add a candidate to a job's hiring pipeline and interview process - Track the source of th
- Create CandidateCreate a new candidate in the system. Use this to add candidates with their contact information and social profiles before applying them to jobs.
- Create Custom FieldCreate a new custom field in Ashby. Custom fields allow you to track additional structured data on Ashby objects like candidates, applications, and jobs. This action creates the field definition that
Show all 62
- Create JobCreate a new job opening in Ashby ATS. Use this action to: - Add a new role to your organization with a title, department, location, and brand - Set up the job structure before publishing or opening i
- Create OfferCreate a new offer for a candidate in Ashby ATS. Use this to generate formal job offers with all required field values after starting an offer process and obtaining the form definition. Prerequisites:
- Create OpeningCreate a new opening (job requisition) in Ashby ATS. An opening represents a job requisition - a request to hire for a specific position. All parameters are optional, but typically you'll want to prov
- Create ReferralCreate a referral in Ashby ATS by submitting a referral form with candidate information. Use this action to formally submit employee referrals for job openings, which creates both a candidate record (
- Create Survey RequestGenerate a survey request and receive a survey URL to send to a candidate. Use this when you need to collect feedback or information from candidates via a survey. Requires candidatesWrite permission.
- Remove Opening JobRemove a job from an opening (job requisition) in Ashby ATS. Use this action to disassociate a job from a specific opening. This is useful when: - A job was added to the wrong opening - You need to re
- Remove Opening LocationTool to remove a location from an opening (job requisition). Use when you need to disassociate a location from an existing opening. Requires the jobsWrite permission.
- Set Custom Field ValueSet the value of a custom field for a given object (candidate, application, job, etc.). Use when you need to update a single custom field value. Important: When updating multiple custom fields on the
- Set Custom Field ValuesSet the values of multiple custom fields for a given object in a single call. Use when you need to update multiple custom fields on the same object (candidate, application, job, or opening). This is t
- Set Job StatusSet the status of a job in Ashby ATS (Applicant Tracking System). Use this action to change the workflow state of a job: - Set to 'Open' to make a job actively accept applications - Set to 'Closed' to
- Set Opening StateSet the workflow state of an opening (job requisition). Use this to transition an opening between states: Draft, Approved, Open, or Closed. Important notes: - When setting state to 'Closed', you must
- Start OfferCreate a new offer version instance for an in-progress offer process. The returned offer version can be filled out and submitted using the Create Offer action. Use this action before creating a finali
- Start Offer ProcessStart an offer process for a candidate's application in Ashby ATS. Use this action when you need to initiate the formal offer workflow for a candidate who has progressed through interviews and is read
- Submit Application FeedbackSubmit structured feedback for an application using a feedback form. Use this for formal interview feedback and scorecards, not for informal notes or comments.
- Transfer ApplicationTransfer an application to a different job position in Ashby ATS. Use this action to move a candidate's application from one job opening to another while optionally preserving their application histor
- Update ApplicationUpdate an application's properties in Ashby. Use this action to modify application metadata such as: - Source attribution (how the candidate found or was found for the job) - Credited user (who should
- Update Application HistoryUpdate the complete history of an application's stage transitions. Use this to modify stage entry times, delete history events, or update existing history records. CRITICAL: This endpoint requires sen
- Update CandidateUpdate an existing candidate's profile information in Ashby ATS. Use this action to modify candidate details like name, email, phone number, job title, company, school, and social profiles (LinkedIn,
- Update Job CompensationUpdate a job's compensation tiers in Ashby ATS. Use this action to define or modify the compensation structure for a job posting. You can specify multiple tiers (e.g., 'Junior', 'Senior', 'Staff') and
- Update JobUpdate an existing job's properties in Ashby ATS. Use this action to modify job details such as: - Job title (e.g., change "Engineer" to "Senior Engineer") - Department/team assignment - Office locati
- Update OpeningUpdate properties of an existing opening (job requisition). Use this to modify opening details such as description, team, hire dates, and employment type. Requires jobsWrite permission.
- Anonymize CandidateAnonymize 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 candid
- Archive DepartmentArchive 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 departmen
- Archive Interviewer PoolArchive 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 lon
- Archive LocationArchives 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 opera
- Create Candidate NoteCreate a note on a candidate profile. Use this to add comments, observations, or feedback about a candidate during the recruitment process.
- Create Candidate TagCreate a new candidate tag in Ashby for categorizing and organizing candidates. Tags are labels that help you filter, search, and group candidates for better organization and workflow management. Use
- Create DepartmentCreate a new department. Use this to add organizational departments or teams for structuring jobs and hierarchy.
- Create Interviewer PoolCreate a new interviewer pool. Use this to organize interviewers into groups by expertise or interview type. Requires the hiringProcessMetadataWrite permission.
- Create LocationCreate a new location or location hierarchy. Use this to add office locations, remote work settings, or nested location structures for organizational management.
- Create Survey SubmissionCreate a new survey submission for a candidate's application. Use this to submit candidate survey responses programmatically, such as candidate experience ratings or feedback forms. Requires the candi
- Get Referral FormFetches the default referral form or creates a default referral form if none exists. Requires the hiringProcessMetadataRead permission.
- Move DepartmentTool to move a department to another parent in the organizational hierarchy. Use when reorganizing department structure or changing parent-child relationships. Requires the organizationWrite permissio
- Move LocationTool to move a location to a different parent in the location hierarchy. Use when reorganizing location structure or changing parent-child relationships. Requires the organizationWrite permission.
- Remove Hiring Team MemberRemove an Ashby user from a hiring team at the application, job, or opening level. Use this when you need to unassign a team member from participating in the hiring process. Requires the jobsWrite per
- Remove User from Interviewer PoolRemove a user from an interviewer pool. Use this to unassign interviewers from specific interview pools when they should no longer be part of that pool's roster. This removes the user from either the
- Restore DepartmentRestore an archived department by its unique identifier. Restoring a department marks it as active again, making it available in active department lists and allowing it to be used for new jobs and org
- Restore Interviewer PoolRestore an archived interviewer pool in Ashby. This unarchives the pool, making it available again for new interview assignments. Use this when you need to reactivate an interviewer pool that was prev
- Restore LocationRestores an archived location or location hierarchy in Ashby. When restored, the location is marked as active (isArchived=false) and becomes available again for job postings, assignments, and other lo
- Set Opening ArchivedSets the archived state of an opening. Requires the jobsWrite permission. Use this to archive or unarchive job openings.
- Update DepartmentUpdate an existing department's information such as its name. Use this action to: - Rename a department to reflect organizational changes - Update department names with Unicode/international character
- Update Interviewer PoolUpdate an existing interviewer pool's title or training requirements. Interviewer pools are groups of interviewers organized by expertise or role (e.g., "Backend Engineers", "Bar Raiser Interviews").
- Update Job PostingUpdate an existing job posting's details including title, description, and visibility status. This action allows you to modify public job postings properties such as: - Title: Change the job posting t
- Update Location AddressUpdate the address of a location or location hierarchy. Use this when you need to modify location address details such as city, region, country, or postal code. Requires the organizationWrite permissi
- Update Location External NameUpdate a location's external (candidate-facing) name. Use this to set or clear an alternate name for a location that is displayed on job boards and used in the API.
- Update Location NameUpdate a location's name. Use this to rename an existing location. Requires the organizationWrite permission.
- Update Location Remote StatusTool to update a location's remote status. Use when you need to mark a location as remote or non-remote. Requires organizationWrite permission.
- Update Location Workplace TypeTool to update a location's workplace type (OnSite, Remote, or Hybrid). Use when you need to modify the workplace setting for an office location. Requires organizationWrite permission.
- Update Selectable Values Custom FieldUpdate the selectable values for a ValueSelect or MultiValueSelect custom field. Use this to add new options, modify existing option labels, or archive outdated options. Values are merged with existin
- Update User Interviewer SettingsUpdate interviewer settings for a user, including daily and weekly interview limits. Use this when you need to set or modify interview scheduling constraints for a user. Either limit can be provided i
Changes wait in Needs you
Changes and sends in Ashby are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Ashby questions
Can an agent change data in Ashby on its own?
Not by default. Changes and sends in Ashby are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Ashby?
This connector lists 63 read actions. Reads run at once, without waiting for approval.
How does Ashby connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.