[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)

# Reject Ashby candidates and send the rejection email

> Archive Ashby applications by your own rule with the right archive reason and rejection email, and keep the unclear ones for a recruiter.

Source: https://cotlet.dev/integrations/ashby-api-mcp-server/reject-candidates-and-send-rejection-emails

A job closes its first screen, 60 applications sit in Application Review, and a recruiter opens each one, picks an archive reason and an email template before moving to the next.

Cotlet does it in your own Ashby account with list\_applications, get\_candidate, list\_archive\_reasons and archive\_application, 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 offers three native ways (checked 16 Oct 2026): Archive in Application Review, bulk archive from candidate search, and Auto-reject on conditions. The official MCP has no reject tool, and its stage tool is described as moving an application to another interview stage. Nothing in Ashby reads a resume and your notes, then picks a reason per person.

## How you do it in Ashby today

1. In Application Review, or on the candidate profile, the recruiter clicks Archive for the application.
2. Ashby asks for one archive reason from the list an admin keeps under Admin > Jobs & Applications > Archive Reasons; a note is optional.
3. The recruiter picks a rejection email template, a from address, and sends it immediately or schedules it.
4. For many at once, candidate search can bulk archive applications and schedule the rejection email, or Auto-reject can archive on conditions such as an answer on the application form.
5. The reason then shows in the Archived stage under Activities & Progress > Interview Progress, with the note behind Details.

## How to reject Ashby candidates and send the rejection email

Prompt

```
List active applications in the Senior Backend Engineer job that sit in Application Review and were submitted more than 14 days ago. Reject the ones whose resume shows under 3 years of backend work with the archive reason "Not a fit", send the rejection email template "After screen" and show me the rest.
```

1. 01  
### Pull the screen queue  
Your agent lists active applications of one job with list\_applications, filtered by the stage name and an updated\_before date, and pages until the queue is complete.
2. 02  
### Read before deciding  
For each application get\_candidate returns the resume summary, notes and earlier emails, so a candidate a colleague already flagged is never rejected by rule alone.
3. 03  
### Map the rule to a reason  
list\_archive\_reasons gives the exact reason names your admin set up. The agent picks only from that list; if none fits, it leaves the candidate for you instead of inventing a reason.
4. 04  
### Archive with the email  
archive\_application runs for the clear matches with the reason, an optional note and the rejection template. Each call waits for your OK by default, because the candidate gets an email.
5. 05  
### Report the rest  
Applications that do not match are listed with one line on why, so you can decide on them by hand.

### What you get back

Example data

```
Job: Senior Backend Engineer, stage Application Review, older than 14 days: 22
Archived 14 with reason "Not a fit", email "After screen" sent:
- Chris Nowak: 1 year of backend work
- Dana Rossi: only frontend roles
Left for you 8:
- Mei Tanaka: strong resume, but a note from Priya says "call back in Q1"
- Omar Haddad: resume missing
```

### Other ways to ask

- Every Monday, archive applications older than 30 days in any job with the reason "Position filled", and schedule the email for 9:00 the next morning.
- Show me which of these 22 applications you would reject and why, but do not archive anyone yet.
- Reject everyone who answered "No" to the work authorization question, with no email, and list their names.

## What Ashby allows, and what to know first

- Ashby requires an archive reason on every archive, and the list of reasons is set by an admin under Admin > Jobs & Applications > Archive Reasons.
- The rejection email can be sent right away or scheduled, and only the person who drafted a scheduled email can view or reschedule it.
- Archiving rejects the candidate for that job only and moves them to the Archived stage of that interview process.
- In Application Review the reason is required before a candidate can be rejected, and the email needs a template and a from address.
- Ashby lets an organization set a default archive reason and a default rejection email on its Application Review page.

archive\_application asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.

Sources: [Ashby Knowledge Base: Candidate Profile](https://docs.ashbyhq.com/candidate-profile) · [Ashby Knowledge Base: Application Review](https://docs.ashbyhq.com/application-review) · [Ashby product update: Bulk archive applications from candidate search](https://www.ashbyhq.com/product-updates/bulk-archive-applications-from-candidate-search) · [Ashby product update: Pre-screen candidates with Auto-reject](https://www.ashbyhq.com/product-updates/pre-screen-candidates-with-auto-reject)

## Call archive\_application from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/ashby/applications/7d2e4c18-5f3a-4b09-8a61-c0e9d3f1a742/archive \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"archive_reason":"Not a fit","note":"About 1 year of backend work; the role asks for 3 or more.","email_template":"After screen","send":"immediately"}'
```

Example response

```
{
"application_id": "7d2e4c18-5f3a-4b09-8a61-c0e9d3f1a742",
"status": "Archived",
"archive_reason": "Not a fit",
"note_added": true,
"rejection_email": {
"template": "After screen",
"status": "sent"
}
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is ashby\_write → archive\_application. 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 reject Ashby candidates and send the rejection email__
| Tool | Parameters |
| ---------------------- | ----------------------------------------------------------------------- |
| list\_applications | job\_id, stage, updated\_before, archived, cursor |
| get\_candidate | candidate\_id |
| list\_archive\_reasons | none |
| archive\_application | application\_id, archive\_reason, note, email\_template, send, send\_at |

[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

- [Schedule Ashby interviews for candidates in a stage](https://cotlet.dev/integrations/ashby-api-mcp-server/schedule-interviews-for-candidates.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.