Manatal logo Manatal automation · runs weekly

Drop stale Manatal candidates with a drop 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 All Manatal tools

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 · Manatal Help: Drop Reasons · Manatal Help: Candidate Matches Page · Manatal Help: 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

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

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.

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