Definite runs as a private deployment in your own cloud (AWS, GCP, Azure, or anywhere with Kubernetes); you keep control of data, compute, and networking. Explore private deployment →
Explore with AI
ChatGPTClaudeGeminiPerplexity
← All connectors/HR & People
Ashby
§ Connector
Ashby

Analyze your Ashby data with AI today.

Build dashboards, automate reports, and ask questions in plain English — all from your Ashby data, no complex infrastructure to maintain.

Want it to watch your Ashby data and act on its own? Meet the Ashby agent →

§ Live with
§ What you get

Everything Ashby exposes, modeled and queryable.

Ashby is an applicant tracking system (ATS) and recruiting platform. This connector syncs candidates, applications, jobs, interviews, offers, and the supporting taxonomy (departments, locations, sources) for recruiting funnel and hiring analytics.

Standard on every Definite connector
Sync cadence
Hourly or faster
CDC
Native where supported
Auth
Standard
Row-level security
Yes

Tables & streams

15 objects
◆Candidates

People in the recruiting pipeline with contact and profile details. Used to analyze talent pool size, candidate sourcing quality, and demographic or geographic distribution of applicants.

operationsgeneral_data_storage
◆Applications

A candidate's application to a specific job, including stage and status. Used to measure pipeline conversion, funnel drop-off by stage, and time-to-hire.

operations
◆Jobs

Internal job requisitions being recruited for. Used to track open headcount, hiring velocity per role, and requisition aging.

operations
◆Job Postings

Public-facing postings for jobs, with department, location, and team metadata. Used to analyze job board performance and posting reach.

operationsmarketing
◆Interviews

Individual interview events conducted with candidates. Used to measure interview load, interviewer activity, and scheduling efficiency.

operations
◆Interview Schedules

Scheduled interview sessions tied to applications. Used to track scheduling throughput and interview cycle time.

operations
◆Interview Stages

Stages within an interview plan that applications progress through. Used to model the recruiting funnel and stage-level conversion.

operations
◆Offers

Employment offers extended to candidates. Used to track offer acceptance rate, offer-to-hire conversion, and compensation trends.

operationsrevenue_finance
◆Feedback Form Definitions

Templates defining structured interview feedback and scorecards. Used to standardize evaluation criteria and analyze interviewer scoring.

operations
◆Application Criteria Evaluations

Scored evaluations of applications against defined hiring criteria. Used to analyze candidate quality and evaluation consistency.

operations
◆Sources

Channels through which candidates entered the pipeline (referrals, job boards, agencies). Used for source-of-hire attribution and sourcing ROI.

operationsmarketing
◆Archive Reasons

Reasons applications are archived or rejected. Used to analyze rejection patterns and pipeline drop-off causes.

operations
◆Departments

Organizational departments associated with jobs. Used to segment hiring metrics by department.

operationsgeneral_data_storage
◆Locations

Office or geographic locations tied to jobs and postings. Used to segment hiring activity by region.

operationsgeneral_data_storage
◆Users

Ashby platform users such as recruiters, hiring managers, and interviewers. Used to attribute recruiting activity and measure team workload.

operationsgeneral_data_storage
§ How it works

Three steps. One afternoon.

01
Connect

Authenticate Ashby in a few clicks. OAuth, API key, or IAM role — we handle secrets and rotation.

definite connect ashby
02
Sync

We pull every stream into your warehouse. CDC where the API supports it; full + incremental otherwise. Hourly-or-faster, row-level secure.

→ ashby.raw (synced hourly)
03
Query

SQL, dashboards, or ask Fi in plain English. Your Ashby data lives next to every other source — ready to join.

SELECT * FROM ashby.*
Explore analytics for Ashby

Watch how Definite connects your sources and turns data into answers.

Watch the demo →
*
Don't see yours?
Any API becomes a Definite connector.

Build your own with the Definite SDK, or request it. Most go live in days.

Request a connector →
§ Combine with your stack

Pair Ashby with the rest of your data.

Join Ashby with the rest of your data, then ask Fi questions across all of it.

Your answer engine
is one afternoon away.

Watch the walkthrough to see how Definite connects your data and answers questions.