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

# Drop stale Manatal candidates with a drop reason

> Clear the Applied stage of a Manatal job weekly: drop candidates who went quiet, each with a drop reason from your list, and keep the rest.

Source: https://cotlet.dev/integrations/manatal-api-mcp-server/drop-candidates-with-reason

The Applied stage of an open job fills up faster than anyone clears it, and every candidate who went quiet still sits there next to people you want to call.

Cotlet does it in your own Manatal account with search\_jobs, list\_job\_pipeline, list\_drop\_reasons and drop\_candidate, called by your AI agent, an n8n workflow or a script.

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

Hosted · nothing to install or maintain

## Can Manatal do this on its own?

Manatal's MCP server has list\_drop\_reasons and bulk\_drop\_matches, Enterprise Plus only (checked 20 Oct 2026). On Professional and Enterprise there is no API or MCP, and the Drop option sits on each candidate's card in the pipeline.

## How you do it in Manatal today

1. Open the job and its Pipeline view.
2. Click the three dots on a candidate's card and choose Drop.
3. Select the reason for dropping the candidate and click Save.
4. Repeat for each candidate, stage by stage, job by job.
5. Nobody notices a stale card until the stage is long, so the clean-up waits for a quiet afternoon that does not come.

## How to drop stale Manatal candidates with a drop reason

Prompt

```
In the Product Designer job, drop everyone still in Applied for more than 30 days with the reason No response, and tell me who you skipped.
```

1. 01  
### Open the stage  
Your agent finds the job with search\_jobs and reads the Applied stage with list\_job\_pipeline, following next\_cursor until the stage is complete.
2. 02  
### Age the candidates  
Each candidate carries added\_to\_job\_on, the date Manatal shows as Added to Job on. It is filled only when an admin has turned on Candidate Matches. If it is empty, the agent says so and asks you for another rule instead of guessing ages.
3. 03  
### Pick the reason  
list\_drop\_reasons returns your account's own reasons. The agent uses the one you named, and if none of them fits it stops and asks. It never creates a reason, because only an admin edits that list.
4. 04  
### Drop one by one  
drop\_candidate runs for each match older than your limit. Dropping changes how the application is treated for the team, so each call waits for your OK by default; you can approve the whole batch once or switch confirmation off for this tool.
5. 05  
### Check before each drop  
Right before a drop, the agent reads the stage again. A candidate a colleague moved to Interview in the meantime is no longer in Applied, so the agent skips that person.

### What you get back

Example data

```
Job: Product Designer, stage Applied: 14 candidates
Older than 30 days: 6
Dropped 5 with reason No response
Skipped 1: Priya Nair moved to Interview this morning
Still in Applied: 8
```

### Other ways to ask

- Every Friday, drop candidates in Applied for 21 days or more with the reason Not a fit, in all my open jobs, and list the names.
- List who would be dropped from Sales Manager Applied, but drop no one until I say yes.
- Drop the three candidates I name in Product Designer with the reason Withdrew.

## What Manatal allows, and what to know first

- Manatal says dropping marks a candidate as no longer considered for the position, while the profile stays in your database for future jobs.
- The reason you pick stays on the candidate's profile for reference.
- Drop reasons are managed under Administration by an admin, and a change applies to every user in the company account.
- Manatal tracks Added to Job on, Submitted on, Interviewed on, Received Offer on and Hired on for each match once an admin enables Candidate Matches.

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

Sources: [Manatal Help: Drop a Candidate](https://support.manatal.com/docs/drop-a-candidate) · [Manatal Help: Drop Reasons](https://support.manatal.com/docs/drop-reasons) · [Manatal Help: Candidate Matches Page](https://support.manatal.com/docs/candidate-match) · [Manatal Help: MCP Server](https://support.manatal.com/docs/mcp-server)

## Call drop\_candidate from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/manatal/match/55120/candidate/drop \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"drop_reason_id":3}'
```

Example response

```
{
"match_id": 55120,
"job_id": 3107,
"status": "dropped",
"reason": "No response",
"profile_kept": true
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is manatal\_write → drop\_candidate. Example data.

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

## Manatal tools this automation uses

__Cotlet Manatal tools used to drop stale Manatal candidates with a drop reason__
| Tool | Parameters |
| ------------------- | ------------------------------- |
| search\_jobs | query, organization\_id, cursor |
| list\_job\_pipeline | job\_id, stage, cursor |
| list\_drop\_reasons | none |
| drop\_candidate | match\_id, drop\_reason\_id |

[All 13 Manatal tools with descriptions](https://cotlet.dev/integrations/manatal-api-mcp-server.md#tools)

## Frequently asked questions

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

Yes. You sign in to Manatal yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Manatal 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 Manatal automations

- [Log interview feedback as Manatal candidate notes](https://cotlet.dev/integrations/manatal-api-mcp-server/log-interview-feedback-notes.md)
- [Add a shortlist of candidates to a Manatal job](https://cotlet.dev/integrations/manatal-api-mcp-server/shortlist-candidates-for-a-job.md)
- [Manatal API and MCP server: every tool](https://cotlet.dev/integrations/manatal-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Manatal.

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

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

---

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.