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

# Reply to new Homerun applicants on time

> Answer Homerun applicants whose first reply is overdue with a personal email that fits their application, and log it on the profile. Runs daily.

Source: https://cotlet.dev/integrations/homerun-api-mcp-server/reply-to-new-applicants

Homerun sends a confirmation email the moment someone applies, but that is not a reply, and the applicants who wait longest are the ones nobody opens first.

Cotlet does it in your own Homerun account with list\_candidates, get\_candidate, send\_candidate\_email and add\_candidate\_note, 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's Public API can send the application confirmation email once per application, and nothing else by email (checked 22 Oct 2026). Homerun can send template emails and bulk emails from the app, and it flags overdue replies, but it does not write a reply that fits each application.

## How you do it in Homerun today

1. Homerun marks a candidate "First reply overdue" on the job overview page and on the profile once the set number of days has passed since the confirmation email.
2. An admin sets that number in Settings under Hiring process, First reply status, to 3, 5, 7, 14 or 30 days, or per job in the job settings.
3. To reply, open the job, choose Candidates, open the profile and click the Message button, then write the email or pick an email template.
4. Choose Send to send it at once, or schedule it for later; the email shows in the Activity and message modal of the candidate.
5. The status disappears once a reply is sent, so the work is a daily scan of the overdue list and a fresh email for each person.

## How to reply to new Homerun applicants on time

Prompt

```
Find candidates in Customer Success Manager whose first reply is overdue. Send each a short personal reply that mentions one thing from their application and says when we decide. Skip anyone I already wrote to.
```

1. 01  
### Find who is waiting  
list\_candidates runs per job and keeps the candidates flagged as first reply overdue. The flag follows the timeframe your account set, so the agent never invents its own deadline.
2. 02  
### Read the application  
get\_candidate brings the answers, the stage and the messages already exchanged. A candidate with an earlier message from you is skipped, because a second greeting reads like a bot.
3. 03  
### Write one reply each  
The email names one concrete thing from the application and gives the next step and the date you gave in your prompt. Placeholders and one template for everyone are what the app does by itself; this is the personal part.
4. 04  
### Send under your name  
send\_candidate\_email goes through Homerun, so it lands in the candidate's message panel with the rest of the conversation. Each email waits for your OK until you switch confirmation off for it.
5. 05  
### Log what was sent  
add\_candidate\_note adds a one-line internal note, for example that the first reply went out and which date was promised, so a colleague sees it on the profile.

### What you get back

Example data

```
Candidates with first reply overdue: 9
Replied to 7, e.g. Priya Raman: mentioned her onboarding project, decision by Friday
Skipped 2 (you already wrote to them)
Note added to all 7 profiles
```

### Other ways to ask

- Every morning, reply to overdue candidates in all active jobs and list the ones you could not answer.
- Draft the replies for the overdue candidates in this chat and send nothing until I say so.
- Write to the candidates I disqualified this week with a polite two-line message and no reason.
- Reply only to candidates who rated their own experience above 3 years in the application form.

## What Homerun allows, and what to know first

- The confirmation email does not count as a first reply in Homerun, so a candidate stays overdue until you write to them.
- The first reply timeframe can be 3, 5, 7, 14 or 30 days, and switching the status off changes it for everyone in the account.
- Replies from a candidate show in the message modal, as a notification when enabled, and in your inbox.
- Homerun can send an email from your company name or your personal name, a setting kept in the account.
- A bulk email in Homerun cannot be sent from the Talent pool, only from a job's candidate list.

send\_candidate\_email 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 consistently reply on time to every application](https://help.homerun.co/en/articles/3801831-how-to-consistently-reply-on-time-to-every-application) · [Homerun Help: How to email candidates](https://help.homerun.co/en/articles/4965967-how-to-email-candidates) · [Homerun Help: Candidate communication](https://help.homerun.co/en/articles/5016489-candidate-communication) · [Homerun Public API documentation](https://developers.homerun.co/)

## Call send\_candidate\_email from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/homerun/jobs/job_3b7e91/candidates/ap_K2mP7rS1uW5yA9bC3dE6/email \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"Hi Priya, thanks for applying. Your onboarding project at Northwind is exactly what this role is about. We decide on interviews by Friday and I will write to you then."}'
```

Example response

```
{
"candidate_id": "ap_K2mP7rS1uW5yA9bC3dE6",
"status": "sent",
"sent_at": "2026-10-22T09:12:00Z"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is homerun\_write → send\_candidate\_email. 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 reply to new Homerun applicants on time__
| Tool | Parameters |
| ---------------------- | ---------------------------- |
| list\_candidates | job\_id, stage, tag, status |
| get\_candidate | job\_id, candidate\_id |
| send\_candidate\_email | job\_id, candidate\_id, body |
| add\_candidate\_note | job\_id, candidate\_id, text |

[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)
- [Close Homerun jobs when they have enough applicants](https://cotlet.dev/integrations/homerun-api-mcp-server/close-jobs-with-enough-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.