[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Schedule Ashby interviews for candidates in a stage

> Schedule Ashby interviews for every candidate waiting in a stage, with the right interviewers, video link and invite, and skip anyone already booked.

Source: https://cotlet.dev/integrations/ashby-api-mcp-server/schedule-interviews-for-candidates

Five candidates reached the technical screen this week, and a coordinator opens each profile, picks an interview type, adds interviewers and chooses invite settings five times over.

Cotlet does it in your own Ashby account with list\_applications, get\_candidate, list\_interviews and schedule\_interview, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=ashby) [All Ashby tools](https://cotlet.dev/integrations/ashby-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Ashby do this on its own?

Ashby has native options for this job (checked 16 Oct 2026): Manual Schedule, candidate availability requests and direct booking links. The official MCP has no scheduling tool: get\_upcoming\_interviews and get\_interview\_details only read your own interviews. Nothing in Ashby books a batch of candidates from one instruction.

## How you do it in Ashby today

1. On the candidate profile, the coordinator clicks More > Schedule New Interview > Manual Schedule, or + New Interview > Schedule Interview > Manual Schedule.
2. On the calendar screen they set the date, pick the interview type, use Add interviewer slot for each interviewer and set the start time and length.
3. On the communications step they choose Send and notify candidate or Don't send calendar invites, then a Location Type: Google Meet, Zoom, Microsoft Teams or custom text.
4. The Candidate Confirmation Email tab has a Send Candidate Confirmation Email toggle, Off by default for interviews created from scratch.
5. They click Schedule, then repeat the whole sequence for the next candidate.

## How to schedule Ashby interviews for candidates in a stage

Prompt

```
For candidates who just moved to Technical Screen in the Senior Backend Engineer job, schedule the "Technical screen" interview with priya.nair@example.com for the first free slot on Thursday at 14:00, send the invite to the candidate and add a Google Meet link.
```

1. 01  
### Find who is waiting  
list\_applications returns active applications in the stage you named, and get\_candidate shows which of them already have an interview of that type, so nobody is booked twice.
2. 02  
### Check the interviewer is free  
list\_interviews shows the interviews already booked on that day, so the agent can warn about a clash before it creates anything.
3. 03  
### Respect the invite choices  
The agent passes exactly the invite settings from your prompt: notify the candidate or not, notify interviewers or not, the video provider and whether the confirmation email goes out.
4. 04  
### Schedule one by one  
schedule\_interview runs once per candidate, and each call asks for your OK by default because the candidate and the interviewers receive a calendar invite.
5. 05  
### Report the result  
Each booking is returned with time, interviewers and link; candidates the agent skipped come back with the reason.

### What you get back

Example data

```
Stage Technical Screen, job Senior Backend Engineer: 5 candidates
Scheduled 3 for Thu 22 Oct, 14:00, 14:45 and 15:30 with Priya Nair, Google Meet
Skipped 2:
- Lena Fischer: already has a Technical screen on Fri 23 Oct
- Tom Reyes: Priya has a clash at 15:30
```

### Other ways to ask

- Every morning, schedule the "Recruiter call" for new candidates in the Recruiter Screen stage with Ana Costa, but do not send calendar invites to the candidate.
- List the candidates in Onsite who have no interview booked yet, but do not schedule anything.
- Schedule this candidate's three onsite interviews on the same day with these three interviewers, one hour each.

## What Ashby allows, and what to know first

- Ashby allows manual interview scheduling for Elevated Access Hiring Managers and Admins, Admin (Private) users and Organization Admins, and not for Limited Access, Analyst or Hiring Team Member users.
- With the Don't send calendar invites option the schedule exists in Ashby only and does not appear on anyone's calendar.
- Google Meet, Zoom and Microsoft Teams options generate a unique video link for each invite.
- The calendar of an interview cannot be changed when it is rescheduled, so Ashby recommends a shared calendar.
- The Candidate Confirmation Email is Off by default for interviews created from scratch and must be switched on per interview.

schedule\_interview asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [Ashby Knowledge Base: Manually Scheduling Interviews](https://docs.ashbyhq.com/manually-scheduling-interviews) · [Ashby Knowledge Base: Candidate Profile](https://docs.ashbyhq.com/candidate-profile) · [Ashby Knowledge Base: Setting Scheduling Defaults](https://docs.ashbyhq.com/setting-scheduling-defaults) · [Ashby Knowledge Base: Ashby MCP Server (Beta)](https://docs.ashbyhq.com/ashby-mcp-server-beta)

## Call schedule\_interview from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/ashby/applications/2b9f6e04-1c7d-4a35-b8e2-5d0a93c47f16/interview/schedule \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"interview":"Technical screen","start":"2026-10-22T14:00:00+02:00","duration_minutes":45,"interviewers":["priya.nair@example.com"],"location_type":"google_meet","notify_candidate":true,"notify_interviewers":true,"confirmation_email":false}'
```

Example response

```
{
"interview_id": "f4a1c096-3d78-4e25-8b9c-0a6e57d2b813",
"interview": "Technical screen",
"start": "2026-10-22T14:00:00+02:00",
"duration_minutes": 45,
"interviewers": [
"priya.nair@example.com"
],
"location": "Google Meet",
"candidate_invited": true,
"confirmation_email_sent": false
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is ashby\_write → schedule\_interview. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/ashby-api-mcp-server.md#automations)

## Ashby tools this automation uses

__Cotlet Ashby tools used to schedule Ashby interviews for candidates in a stage__
| Tool | Parameters |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| list\_applications | job\_id, stage, updated\_before, archived, cursor |
| get\_candidate | candidate\_id |
| list\_interviews | candidate\_id, from, to |
| schedule\_interview | application\_id, interview, start, duration\_minutes, interviewers, location\_type, location, notify\_candidate, notify\_interviewers, confirmation\_email |

[All 12 Ashby tools with descriptions](https://cotlet.dev/integrations/ashby-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Ashby to Cotlet?

Yes. You sign in to Ashby yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Ashby once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Ashby automations

- [Reject Ashby candidates and send the rejection email](https://cotlet.dev/integrations/ashby-api-mcp-server/reject-candidates-and-send-rejection-emails.md)
- [Create an Ashby offer and send the offer letter](https://cotlet.dev/integrations/ashby-api-mcp-server/create-and-send-offers.md)
- [Ashby API and MCP server: every tool](https://cotlet.dev/integrations/ashby-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Ashby.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Ashby.

[Sign up free](https://cotlet.dev/app/signup?app=ashby)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.