A
ATS / Recruiting

Ashby AI Integration

Connect Ashby to BeforeQuery for grounded AI answers and agent actions across ATS / Recruiting.

Connect Ashby
What is it?

About Ashby

Ashby is one of the ATS / Recruiting platforms BeforeQuery connects to. Once linked, the platform's data becomes a first-class source for grounded AI answers and a target for policy-gated agent actions — the same identity, approval, and audit-log guarantees every other integration ships with.

Setup

How to connect Ashby

  1. Step 01

    In the BeforeQuery dashboard, go to Integrations → ATS / Recruiting and select Ashby.

  2. Step 02

    Sign in to Ashby with an account that has permissions to grant BeforeQuery the ATS / Recruiting scopes required.

  3. Step 03

    Confirm the connection. Ashby is now available as a source and action target for every playbook in your workspace.

Explore

Related integrations

BH
Breezy HR

Breezy HR is one of BeforeQuery's ATS / Recruiting integrations. Connect it once and every agent in your workspace can read, reason over, and act on Breezy HR data with your policies + audit trail.

B
Bullhorn

Bullhorn is one of BeforeQuery's ATS / Recruiting integrations. Connect it once and every agent in your workspace can read, reason over, and act on Bullhorn data with your policies + audit trail.

C
Certn

Certn is one of BeforeQuery's ATS / Recruiting integrations. Connect it once and every agent in your workspace can read, reason over, and act on Certn data with your policies + audit trail.

How BeforeQuery uses Ashby

What the agent does with your Ashby connection

  • 01

    Read candidate pipelines from Ashby to give recruiters, hiring managers, and executives live status without opening the ATS.

  • 02

    Draft interview follow-ups, rejection emails, and candidate-experience touch-ups grounded in your interview notes and rubrics.

  • 03

    Auto-tag and route new Ashby candidates by skill match, seniority, or requisition fit.

  • 04

    Coordinate the panel: schedule interviews, send prep packets, collect scorecards — all triggered by Ashby stage transitions.

Use cases

What teams actually do with the Ashby integration

Interview-stage automation

When a candidate advances to on-site in Ashby, a playbook drafts the calendar invites for the panel, sends the candidate a prep packet with your travel-and-logistics doc, and sets a scorecard-due reminder for interviewers 24 hours after the interview.

Rejection email drafts grounded in interview notes

When a candidate is moved to "rejected" in Ashby, BeforeQuery drafts a personalized rejection email that references the specific stage they reached and (optionally, per your policy) high-level feedback — without exposing individual interviewer notes.

Pipeline health digest

Weekly summary of Ashby pipeline movement — new candidates per req, stage-conversion rates, time-in-stage anomalies, upcoming interviews. Delivered to hiring managers in Slack; drill-down back to Ashby on click.

Answer questions grounded in Ashby

Employees and customers ask Ashby-related questions in Slack, Teams, or the widget — BeforeQuery answers with the exact Ashby record shown alongside the response. No context switching, no "log into ATS / Recruiting to check" round-trips.

Ashby — Frequently Asked Questions

Common questions about connecting BeforeQuery to Ashby.

Yes, gated by your approval matrix. Stage-forward moves (schedule interview, extend offer) are typically approver-required; stage-back moves (reject, hold) can be autopilot with a reason logged. All moves reversible via the audit trail.
No — BeforeQuery is read-and-write scoped, not a ranking replacement. Your ATS's own scoring is untouched. BeforeQuery draws on the same data to answer questions, draft communications, and orchestrate downstream actions.
Standard OAuth 2.0 where Ashby supports it, otherwise API-key or bearer-token auth. Credentials are stored encrypted at rest (AES-256-GCM) per workspace, never shared across customers, and rotated on request. The connection is scoped to the least-privilege set of scopes each playbook needs — you approve the scope list on install.
No. Your Ashby data feeds only your workspace's own agents and answers. Nothing is used to train a shared model, and nothing crosses workspace boundaries. Bring-your-own-model is available on Enterprise if you want to pin inference to your own OpenAI / Anthropic / self-hosted deployment.
Yes. Every Ashby integration is scoped at install time — you pick which resources, users, or record types are visible. You can further restrict per-playbook: a single playbook only touches the specific Ashby objects it needs. Scope changes take effect on the next sync.
Every write is logged with the acting user, the playbook that fired it, the exact operation, the target entity IDs, and the timestamp — all in the immutable audit log. Writes are rehearsable in simulation mode against a copy of live data before they touch Ashby for real.

Ready to connect Ashby?

Start free. No credit card required. Connect your first integration in under 5 minutes.

Get started free