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

# Advance Lever candidates after positive interview feedback

> Move Lever candidates to the next pipeline stage once interviewers submitted feedback and the ratings clear your bar. Runs daily.

Source: https://cotlet.dev/integrations/lever-api-mcp-server/advance-candidates-after-feedback

A candidate finishes a phone screen, the interviewer submits a feedback form, and nothing moves until a recruiter opens the profile, reads the rating and changes the stage.

Cotlet does it in your own Lever account with list\_stages, list\_opportunities, list\_feedback and change\_stage, called by your AI agent, an n8n workflow or a script.

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

Hosted · nothing to install or maintain

## Can Lever do this on its own?

Lever's Data API lists feedback and changes a stage (GET /opportunities/:opportunity/feedback, PUT /opportunities/:opportunity/stage) for customers with an API key, and has no MCP server (checked 22 Oct 2026). The help center describes automatic moves only from New Lead; every later move is manual.

## How you do it in Lever today

1. Interviewers fill in the feedback form assigned to them after speaking with the candidate. Admins create the forms under Settings > Feedback.
2. The recruiter opens the opportunity and reads the Feedback section, where submitted feedback shows.
3. To move the candidate, open the opportunity profile and pick the new stage in the stage menu.
4. To move several, select the opportunities in the pipeline list, click Stage in the bulk action toolbar and choose the stage.
5. Lever recommends making the overall rating question required on every feedback form, so each interviewer leaves one rating to read.

## How to advance Lever candidates after positive interview feedback

Prompt

```
For the Phone screen stage of the Senior Designer posting, read the submitted feedback. Move candidates whose every form rates Hire or better to On-site interview and list the rest.
```

1. 01  
### Learn the pipeline  
list\_stages returns your stage names in pipeline order. The agent moves a candidate only one stage forward and only to a stage that exists, because pipelines are customized per account.
2. 02  
### Find the candidates  
list\_opportunities runs with the posting and the stage you name. The agent follows next\_cursor so a long stage is judged as one batch.
3. 03  
### Read the feedback  
list\_feedback is called per candidate. Only completed forms count: a candidate whose interviewer has not submitted stays where they are and goes on your waiting list.
4. 04  
### Apply your bar  
The agent compares each rating with the labels the form itself uses, for example "3 - Hire", and moves a candidate only when every submitted form clears the bar you named. One "No Hire" keeps the candidate in place and puts the form text in your report.
5. 05  
### Move forward, never back  
change\_stage moves the candidate to the next stage. Each call waits for your OK by default, because a wrong move is visible to the team and Lever advises against moving candidates backward.

### What you get back

Example data

```
Phone screen, Senior Designer: 6 candidates
Moved to On-site interview 3 (all forms Hire or better)
Waiting for feedback 2: Aisha Khan, Tom Becker
Staying 1: Dana Whitfield (one form rated No Hire)
```

### Other ways to ask

- Every morning, move candidates in Recruiter screen to Phone screen when the recruiter form says Yes, and list the rest.
- Only show me who would move to On-site interview, do not move anyone yet.
- For all open postings, list candidates who sit in a stage with every form submitted but no decision for a week.

## What Lever allows, and what to know first

- Lever advises against moving candidates backward, because regularly regressing opportunities can skew pipeline data; it suggests creating a new opportunity instead, so the agent only moves forward.
- Changing the stage of one opportunity does not change the stage of the same candidate's other active opportunities.
- Lever moves an opportunity from New Lead to Reached Out when you email it and to Responded when the candidate replies; every move beyond that is done by hand.
- When the posting has an interview plan, the interviewers, interview durations and feedback forms set for a stage are filled in at scheduling, so the forms to expect in Feedback depend on the stage.

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

Sources: [Lever Help: Changing the stage of an opportunity](https://help.lever.co/s/article/Changing-the-stage-of-an-opportunity) · [Lever Help: Understanding pipeline stages](https://help.lever.co/hc/en-us/articles/20087316568477-Understanding-pipeline-stages) · [Lever Help: Best practices for pipeline customization](https://help.lever.co/s/article/Best-practices-for-pipeline-customization) · [Lever Developer: API Overview](https://hire.lever.co/developer/documentation)

## Call change\_stage from a script

curl

```
curl -X PATCH https://cotlet.dev/api/v1/lever/opportunities/9b7e2f40-1c6a-4d83-b5e9-3a8c0d6f4e12/stage \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"stage":"On-site interview"}'
```

Example response

```
{
"opportunity_id": "9b7e2f40-1c6a-4d83-b5e9-3a8c0d6f4e12",
"name": "Marco Silva",
"previous_stage": "Phone screen",
"stage": "On-site interview",
"changed_at": "2026-10-22T09:12:00Z"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is lever\_write → change\_stage. Example data.

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

## Lever tools this automation uses

__Cotlet Lever tools used to advance Lever candidates after positive interview feedback__
| Tool | Parameters |
| ------------------- | ------------------------------------------------ |
| list\_stages | none |
| list\_opportunities | posting\_id, stage, tag, email, archived, cursor |
| list\_feedback | opportunity\_id |
| change\_stage | opportunity\_id, stage |

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

## Frequently asked questions

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

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

- [Archive rejected Lever candidates with a reason and email](https://cotlet.dev/integrations/lever-api-mcp-server/archive-rejected-candidates.md)
- [Add notes to Lever candidate profiles with AI](https://cotlet.dev/integrations/lever-api-mcp-server/log-notes-on-candidate-profiles.md)
- [Lever API and MCP server: every tool](https://cotlet.dev/integrations/lever-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Lever.

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

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

---

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.