Vincere automation · runs weekly
Send a Vincere shortlist to a client as a LiveList
The shortlist is ready on Friday, and someone still has to tick the candidates, pick the job, edit the cover email and decide whether the client sees names.
Cotlet does it in your own Vincere account with list_job_applications, get_candidate and send_candidates_to_client, called by your AI agent, an n8n workflow or a script.
Hosted · nothing to install or maintain
Can Vincere do this on its own?
Vincere has no API for this without a partner agreement and no LiveList action in Zapier (checked 22 Oct 2026). The send is a manual list selection in the app, and the cover email is edited each time.
How you do it in Vincere today
- The recruiter ticks the candidates in the candidate list, then clicks Actions > Send.
- In the pop-up the recruiter picks the Job and chooses whether to include attachments.
- Vincere fills in email template 2.5 - Send Candidate List. The recruiter edits the body, adds recipients and attaches documents.
- The recruiter chooses whether to show or hide candidate names and current employers, then clicks Send.
- The client gets an email with a View Candidates button that opens the job's LiveList.
- For a role with no active job, the recruiter uses Float to Contact, or Float to Distribution List for several recipients.
How to send a Vincere shortlist to a client as a LiveList
For job 1042 in Vincere, send the shortlisted candidates to the client as a LiveList with attachments, names visible. Show me the list before you send. - 01
Read who is ready
list_job_applications with stage shortlisted returns the people waiting on the job. The agent leaves out anyone already at Sent or later, so a client never gets the same candidate twice.
- 02
Check each profile
get_candidate shows current title, company and applications. The agent flags a profile with no title or no CV on file and asks whether to send it anyway.
- 03
Show you the list
Before anything is sent, the agent prints the names, the job, the recipient and whether names are shown or hidden. This is the step to catch a wrong job or a client who must not see a current employer.
- 04
Send once
send_candidates_to_client sends one LiveList per call. It reaches the client, so it waits for your OK by default, and a sent email cannot be recalled through Cotlet.
- 05
Confirm the stage
Vincere moves the applications to Sent when the LiveList goes out. The agent reads the job again and reports any candidate still in Shortlisted.
What you get back
Job 1042: Senior Java Developer, client Alex Reed (Brightline Tech)
Shortlisted candidates: 4
Sent 3 as a LiveList, names visible, attachments included
Held back 1: Tomas Wu has no CV on file
Stage after send: Sent (3) Other ways to ask
- Every Friday, send each client the candidates shortlisted this week for their jobs, and list what you sent.
- Send the LiveList for job 1042 with candidate names and current employers hidden.
- Draft the LiveList cover note for each open job and wait for my OK before sending.
What Vincere allows, and what to know first
- Vincere limits email actions to 100 recipients per send, and a candidate selection holds up to 300 records.
- Vincere lets clients on a LiveList rate candidates, start interviews, reject candidates or mark them KIV, and message the recruiter.
- Vincere keeps a rejected candidate visible in the LiveList with a rejected status, and the application has to be deleted from the job to remove them completely.
- Vincere takes the LiveList columns from Admin Settings > LiveList Settings, and they can be changed per job in Job LiveList Settings.
- Vincere updates the pipeline stage when a LiveList is sent, and a candidate can also be moved to Sent without an email by moving the stage by hand.
send_candidates_to_client asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.
Sources: Vincere Help: Candidate LiveList · Vincere Help: Moving candidates down the Pipeline · Vincere Help: Candidate Actions
Call send_candidates_to_client from a script
curl -X POST https://cotlet.dev/api/v1/vincere/jobs/1042/candidates-to-clients \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"candidate_ids":["88214","88230","88251"],"include_attachments":true,"hide_names":false}' {
"job_id": "1042",
"sent": [
{
"candidate_id": "88214",
"name": "Priya Nair",
"stage": "sent"
},
{
"candidate_id": "88230",
"name": "Tomas Wu",
"stage": "sent"
},
{
"candidate_id": "88251",
"name": "Lena Ortiz",
"stage": "sent"
}
],
"template": "2.5 - Send Candidate List",
"recipients": [
"alex.reed@brightline.example"
],
"names_visible": true,
"attachments_included": true
} MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is vincere_write → send_candidates_to_client. Example data.
Schedule it in n8n, Make, Zapier or cronVincere tools this automation uses
| Tool | Parameters |
|---|---|
| list_job_applications | job_id, stage, limit, cursor |
| get_candidate | candidate_id |
| send_candidates_to_client | job_id, candidate_ids, include_attachments, hide_names, message, extra_recipients |
Frequently asked questions
Is it safe to connect Vincere to Cotlet?
Yes. You sign in to Vincere yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Vincere 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 Vincere.
Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Vincere.