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

# Close Homerun jobs when they have enough applicants

> Close Homerun jobs once they reach the number of applicants you want, so reviewing starts and new applications stop. Runs daily.

Source: https://cotlet.dev/integrations/homerun-api-mcp-server/close-jobs-with-enough-applicants

A popular job post keeps collecting applications while the team is still reading the first batch, and closing it depends on someone noticing the number.

Cotlet does it in your own Homerun account with list\_jobs, list\_candidates and set\_job\_visibility, called by your AI agent, an n8n workflow or a script.

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

Hosted · nothing to install or maintain

## Can Homerun do this on its own?

Homerun closes a job by hand or at a closing date you set (checked 22 Oct 2026). It has no rule that closes a job at a number of candidates, and the Public API reads jobs but cannot change them.

## How you do it in Homerun today

1. Open the Jobs page, hover over the job, click the three dots and choose Closed, or open the job page and choose Closed from the three dots in the top right corner.
2. Alternatively open the job settings with the gear icon, go to General and set a Closing date and time, in UTC unless you pick another time zone.
3. A closed job stays active, so you can still email candidates, schedule interviews and review. Visitors with the link see "Applications closed" instead of "Apply now".
4. Closing by date is fixed in advance. Nothing in Homerun closes a job when the number of candidates reaches a limit.

## How to close Homerun jobs when they have enough applicants

Prompt

```
Check my active public jobs in Homerun. Close every job that has at least 50 candidates in its stages so we stop taking applications, and list what you closed. Leave private jobs alone.
```

1. 01  
### List the active jobs  
list\_jobs runs with state set to active and visibility set to public, so drafts, archived jobs and private jobs are never touched.
2. 02  
### Count the candidates  
list\_candidates counts each job's candidates. Disqualified candidates count only if your prompt says so, so the limit means the same thing every day.
3. 03  
### Close what reached the limit  
set\_job\_visibility moves a job over your limit to closed. The call waits for your OK until you switch confirmation off, because closing changes what visitors and job boards show.
4. 04  
### Report what stays open  
Jobs below the limit are listed with their count, so you see which ones are close and whether to raise or lower the number.

### What you get back

Example data

```
Active public jobs: 5
Closed 2: Customer Success Manager (64 candidates), Product Designer (51 candidates)
Still open 3: Backend Engineer (23), Support Agent (12), Sales Lead (7)
Private jobs skipped: 1 (Office Manager)
```

### Other ways to ask

- Close any job that has been open for more than 30 days, and list how many candidates each had.
- Every Friday, list active jobs with fewer than 10 candidates so I can promote them.
- Reopen closed jobs that dropped below 20 candidates after disqualifications.

## What Homerun allows, and what to know first

- Homerun has three job states, draft, active and archived, and the active state has three visibility statuses, public, private and closed.
- A closed job is still active, an archived job is not: archiving ends communication with the candidates, so finish the hiring process first.
- Closing a job through its closing date also removes it from Google for Jobs, LinkedIn and Indeed if those integrations are on.
- The closing date uses UTC by default, which matters when the job should close at the end of a local day.

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

Sources: [Homerun Help: How to close a job opening for applications](https://help.homerun.co/en/articles/2240859-how-to-close-a-job-opening-for-applications) · [Homerun Help: Homerun's job states explained](https://help.homerun.co/en/articles/9367771-homerun-s-job-states-explained) · [Homerun Help: How to automatically close job openings by setting a closing date](https://help.homerun.co/en/articles/9428450-how-to-automatically-close-job-openings-by-setting-a-closing-date) · [Homerun Help: How to archive a job post](https://help.homerun.co/en/articles/9368611-how-to-archive-a-job-post)

## Call set\_job\_visibility from a script

curl

```
curl -X PUT https://cotlet.dev/api/v1/homerun/jobs/job_9d4a27/visibility \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"visibility":"closed"}'
```

Example response

```
{
"job_id": "job_9d4a27",
"title": "Product Designer",
"state": "active",
"visibility": "closed"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is homerun\_write → set\_job\_visibility. Example data.

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

## Homerun tools this automation uses

__Cotlet Homerun tools used to close Homerun jobs when they have enough applicants__
| Tool | Parameters |
| -------------------- | --------------------------- |
| list\_jobs | state, visibility |
| list\_candidates | job\_id, stage, tag, status |
| set\_job\_visibility | job\_id, visibility |

[All 14 Homerun tools with descriptions](https://cotlet.dev/integrations/homerun-api-mcp-server.md#tools)

## Frequently asked questions

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

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

- [Disqualify unqualified Homerun candidates in bulk](https://cotlet.dev/integrations/homerun-api-mcp-server/disqualify-candidates-in-bulk.md)
- [Reply to new Homerun applicants on time](https://cotlet.dev/integrations/homerun-api-mcp-server/reply-to-new-applicants.md)
- [Homerun API and MCP server: every tool](https://cotlet.dev/integrations/homerun-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Homerun.

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

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

---

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.