Ashby
Connect Ashby so Fours AI can work with your candidates, applications, and job postings.
Overview
Ashby is an applicant tracking and recruiting platform covering sourcing, interviewing, and hiring analytics. Connecting it lets the Fours AI agent read and update your recruiting pipeline — candidates, applications, interviews, and job postings — from a Fours workflow or chat.
Org-Level vs User-Level
Org-Level: Supported. One Ashby API key serves the whole organization.
User-Level: Not applicable. Ashby authenticates with an API key only — it has no OAuth flow of any kind — so there is nothing an individual user could sign in to. Every Fours user in your organization shares the org connection.
How the connection works
Ashby authenticates with HTTP Basic, where the API key is the username and the password is empty. Fours stores the key and builds that header for you, so there is only one field to fill in.
Create Integration (Org-Level)
Prerequisites
- An Ashby account on a plan that includes API access.
- Permission to create an API key in Ashby (Admin settings).
- The Fours Admin role — connecting, disconnecting, and running an integration’s actions are all admin-only in Fours.
Authenticate by API key
- In Ashby, go to Settings → Integrations → API and generate a new API key. Copy it — Ashby shows it once.
- Grant the key the module permissions you want Fours to have. Ashby scopes API keys per module (Candidates, Jobs, Interviews, and so on), so a key missing a module makes every tool for that module fail. Grant read access at minimum, plus write access for anything you want the agent to change.
- In the Fours console, open Settings → Integrations and click Connect on Ashby.
- Paste the key into the single API Key field and save.
Paste the raw key, not a base64 string — Fours builds the Basic header itself. There is no separate username or password to supply.
Fours AI Tools
When Ashby is connected, the Fours AI agent can work your recruiting pipeline through Fours’ built-in tools (23 actions).
Org-level: All tools run under the org API key, so what the agent can see and change is exactly what that key’s module permissions allow.
| Capability | What the agent can do |
|---|---|
| Candidates | Create, read, update, and list candidates (e.g. create-candidate, update-candidate, list-candidates) |
| Applications | Create, read, update, and list applications, and move one between stages or sources (e.g. change-application-stage, change-application-source) |
| Jobs & postings | Read and list jobs and their public postings (e.g. get-job, list-job-postings) |
| Interviews | Read and list scheduled interviews (e.g. get-interview, list-interviews) |
| Notes | Add notes to a candidate record (create-note) |
| Org data | Read and list departments, sources, and users (e.g. list-departments, list-sources, list-users) |
Edit Integration
Editing is not supported. To rotate the key or point Fours at a different Ashby account, delete the integration and create it again.
Delete Integration
Click the 🗑️ button next to Ashby in the Integrations list. The stored key is destroyed with the integration record. Any Fours workflow or agent that depended on Ashby tools stops working immediately. Revoke the key in Ashby too if you want to cut access from that side.
Spotted something wrong or out of date on this page? Tell us and we'll correct it.