Ashby
Connect Ashby and your assistant can work with your recruiting data — candidates, applications, jobs, interviews, offers, and more — so hiring workflows like candidate research, interview prep, and pipeline updates happen without leaving Town.
What’s included
With Ashby connected, your assistant can:
- Search and read recruiting data — candidates, applications, jobs, job postings, interviews, offers, openings, projects, and sources
- Move candidates through your pipeline — create candidates and applications, change stages, add notes and tags
- Work with interviews — list interview plans, stages, and schedules, and create or update schedules
- Manage offers — create, update, approve, and progress offers
- Administer your workspace — create or update jobs and job postings, manage custom fields, manage hiring teams, cancel sequences, push candidates to your HRIS, and anonymize candidates
Connecting Ashby
Ashby connects with an API key. Only an Ashby Organization Admin can create one, and it takes an admin about 2 minutes. If you don’t have admin access, send these steps to your Ashby admin (usually recruiting ops) and ask them to share the key with you.
Step 1: Create an API key in Ashby (admin only)
- In Ashby, go to Admin → Integrations → API Keys
- Click + New, name the key (for example, “Town”), and click Create API key
- Choose permissions. New keys start with no access, so check each area you want your assistant to use and choose Read or Write. Only grant Write where you want your assistant to make changes, like moving candidates between stages or adding notes. (We recommend giving both read and write access because the most useful recruiter routines often involve keeping your ATS up-to-date.)
- Under Other permissions, you can also allow access to confidential jobs and projects
- Click Save and continue, then copy the key. Ashby only shows it once, so save it before closing the window.
For Ashby’s full walkthrough, see How do I generate an API key?
Step 2: Connect Ashby in Town
- Go to Integrations
- Find Ashby and click Connect
- Paste your API key and return to Town
Your assistant can only reach the data and actions the API key allows. To change what it can do, edit the key’s permissions in Ashby. To revoke access, disable the key in Ashby.
What your assistant can do
| Capability | What it does | Makes changes? |
|---|---|---|
| Search candidates and jobs | Find candidates, jobs, and projects | No |
| Read applications and history | View application details, feedback, and history | No |
| List interviews and schedules | See interview plans, stages, events, and schedules | No |
| Read offers and openings | View offer and opening details | No |
| Create and update candidates | Add candidates, notes, tags, and files | Yes |
| Manage applications | Create applications, change stages, submit feedback | Yes |
| Manage interview schedules | Create, update, or cancel schedules | Yes |
| Manage offers | Create, update, approve, and progress offers | Yes |
| Manage jobs and postings | Create or update jobs and job postings | Yes |
| Manage custom fields | Create custom fields and set values | Yes |
| Manage hiring teams | Add or remove hiring team members | Yes |
| Push to HRIS | Send application data to your HRIS | Yes |
| Anonymize candidates | Permanently anonymize a candidate’s data | Yes |
Use cases
- Candidate research — “pull up the candidate profile and latest feedback for my 2pm interview.”
- Pipeline updates — move an application to the next stage after a debrief.
- Interview prep — combine Ashby interview briefings with calendar context.
- Hiring summaries — “summarize this week’s activity across my open roles.”
Good to know
- Recruiting data is sensitive — use approval-required tool settings in routines that change candidate or offer data.
- Some write tools are destructive or reach external systems (anonymizing candidates, pushing to your HRIS) — keep those approval-required.
- Your assistant sees only what the API key allows. If something seems to be missing, check the key’s permissions in Ashby.
Related
- Integrations overview — How integrations give your assistant context
- Routines — Automate recurring recruiting workflows
Town