Homerun logo Homerun automation · runs daily

Close Homerun jobs when they have 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 All Homerun tools

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 · Homerun Help: Homerun's job states explained · Homerun Help: How to automatically close job openings by setting a closing date · Homerun Help: 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

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

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.

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