Candidate Outreach Automation Researched, personalised, followed up twice, stopped on reply
Every candidate gets a first message written from one specific thing they did — and no message when there is nothing specific to say.
- Installed for you · one-time$249
- Run for you$197/month
- Custom build · this process$2,000–3,500 one-time
- Starts whenNew candidate added to an outreach list (ATS project, sheet, CSV)
Per recruiter, up to 400 new candidates a month, email only. LinkedIn steps, multi-language outreach, or an agency running shared sequences across several recruiters are a custom build. Custom builds start at $2,000 site-wide; this band is for this process and its integrations.
Candidate Outreach Automation is an automation Agentmelt installs in Google Sheets. The free template is a file you import yourself; the kit ($49) adds the setup guide and prompts. Installed for you costs $249 one-time and is live within two working days of access, with a recorded walkthrough and 30 days of fixes. Run for you costs $197/month, with setup and maintenance included. A custom build of this process is $2,000–3,500 one-time; custom builds start at $2,000 site-wide. No call is needed for any option. Written by Max Zeshut; last revised 2026-09-21.
Reference stack: Claude + n8n. Node names are on each step; the file is under the template.
Founder at Agentmelt
Reviews every build before it goes live; the workflow escalates to a person, never past one.
What is candidate outreach?
Candidate outreach automation fixes the two reasons recruiting outreach fails — the message is generic and the follow-up never happens: for each candidate on a sourced list the workflow researches their public profile and work, picks one specific hook, drafts a short message that references it, sends it from the recruiter’s own address, follows up twice on a schedule, and stops the sequence the moment the candidate replies. Reply rates by hook and by segment are measured so the recruiter learns what works. The recruiter still owns the list, the role and every conversation; the workflow owns the typing and the calendar.
- Every outreach message starts with ‘I came across your profile’.
- Follow-ups never happen because there are forty other roles.
- Reply rates are under 5% and nobody knows why.
- The recruiter who wrote well left, and the sequences left with them.
- Candidates who replied keep getting the automated follow-up.
If two of these are yours, this is the process to look at first. Free audit — or read on.
What it looks like once it runs.
Recruiting outreach fails for two reasons: the message is generic, and the follow-up never happens. The workflow takes a sourced list, researches each candidate from their public profile and work, drafts a message that references one specific thing they did, sends it from the recruiter's address, follows up twice on a schedule, and stops the sequence the moment the candidate replies — handing the thread to the recruiter with the research attached. Reply rates double against templated outreach, and the recruiter's time goes to conversations, not first messages.
- A candidate is added to the list. Their public profile, company and recent work are researched: three to five facts.
- One hook is chosen — something recent and professional that relates to the role.
- A message under 90 words is drafted: the hook, why the role fits, one question. It sends from your address, spaced under daily limits.
- Day 4 and day 10 Two follow-ups, each a different angle and shorter. A reply stops everything.
A recruiter can write ten good outreach messages a day or fifty bad ones. The good ones get replies; there is no time for them. Follow-ups are forgotten, and the ATS shows 'contacted' next to people who got one message six weeks ago.
Every sourced candidate gets a researched first message and two follow-ups, and the recruiter only sees the ones who replied. Outreach volume goes up without the reply rate going down, and the ATS reflects what actually happened.
Trigger, then 8 steps.
All eight steps run without anyone; a person sees only what the guardrails escalate.
New candidate added to an outreach list (ATS project, sheet, CSV)
Receive the candidate
Name, current title and company, profile URL, and the role they are being sourced for.
Research
Public profile, company page, recent talks or posts, open-source or portfolio work — three to five facts, with sources.
Pick the hook
One specific, recent, professional thing the candidate did that relates to the role. Not their title, not their employer's tagline.
Draft the message
Under 90 words: the hook, why the role is relevant to it, one question. Plain text, no tracking pixels, no 'I hope this finds you well'.
Send from the recruiter
From the recruiter's own address, spaced to stay under daily limits; the ATS gets the message logged against the candidate.
Follow up twice
Day 4 and day 10, each a different angle (the team, the problem, the timing), each shorter than the last.
Stop on reply
Any reply ends the sequence and forwards the thread with the research to the recruiter; an out-of-office pauses it.
Measure
Per role: sent, replied, positive, interviews — by hook type, so the recruiter learns which angles work for which roles.
No step waits for a person.
What the workflow hands to someone, by rule:
- Only public, professional information is used; nothing personal, nothing inferred about protected characteristics.
- Every message is sent from a person's address and signed by that person; replies go to them.
Every sourced candidate gets a researched first message and two follow-ups, and the recruiter only sees the ones who replied
Every sourced candidate gets a researched first message and two follow-ups, and the recruiter only sees the ones who replied.
No decisions needed. Anything the guardrails flag is handed to a person; the rest ran alone.
Each pattern page explains it in plain words and lists every automation that uses it.
The template is built on n8n (how the n8n AI Agent node works); the same steps run on Make, Zapier or plain code. The tool is chosen to fit your accounts, you own the result, and the template comes in all three formats.
Data it touches
- Sourcing list (ATS project, Google Sheet, CSV)
- Public profiles and company pages
- Role brief
- Recruiter voice samples
- ATS for logging
Guardrails
- Only public, professional information is used; nothing personal, nothing inferred about protected characteristics.
- Sending limits: 40 new messages a day per mailbox, spaced, so the recruiter's domain reputation is protected.
- Every message is sent from a person's address and signed by that person; replies go to them.
- Opt-out language in every message; an opt-out suppresses the candidate across all roles.
- Follow-ups stop on any reply, including 'not now', which is logged as a future-contact date.
One specific fact is the whole difference
Candidates can tell within one line whether a message was written for them. 'Saw the migration you led at Northwind' gets a reply; 'I came across your profile' does not. The workflow spends its effort on finding that one fact from public work — a talk, a project, a post, a product they shipped — and refuses to send when it cannot find one, because a generic message costs more in reputation than it earns.
Follow-ups are where the replies are
Most positive replies arrive on the second or third message; most recruiters never send them. The workflow's two follow-ups are scheduled, short, and take a different angle each time, and they stop on any reply. The recruiter never has to remember who to chase.
Sending limits protect the address you cannot replace
A recruiter's own address is the asset. Forty new messages a day, spaced through working hours, plain text, no tracking, sent from a warmed mailbox is what keeps that address landing in inboxes. The workflow enforces the limits rather than trusting the day's enthusiasm.
What it connects to.
| Tool | Role in this workflow |
|---|---|
| n8n | Sequencing, sending, reply detection, logging |
| Claude | Research summary, hook selection, drafting |
| Greenhouse / Lever / Ashby | Sourcing projects and message logging |
| Gmail / Outlook | Sending from the recruiter's address |
| Google Sheets | Outreach list and results |
Want this running without building it?
$197/month
We set it up in your tools, run it on our servershost it on our n8n cloud (or deploy it to your own n8n, Make or Zapier), watch it, and fix it when something changes. Setup included, cancel monthly; the automation stays yours if you leave.
$2,000–3,500 one-time
Your systems, your rules, your edge cases. A one-off build delivered into your accounts to keepon Claude and n8n, delivered into your accounts to keep, with documentation and a recorded walkthrough.
Per recruiter, up to 400 new candidates a month, email only. LinkedIn steps, multi-language outreach, or an agency running shared sequences across several recruiters are a custom build.
Also sold one-time, installed in your own accounts, as part of the recruiters package — do it yourself $49 · installed for you $249 · done for you $490.
When this becomes a custom build.
The subscription covers the standard version — $197/month, setup and maintenance included. Three things move it to a custom build ($2,000–3,500 one-time), delivered into your accounts to keep. If one of them is you, say so on the audit and the plan prices both.
LinkedIn as a channel, with the tooling and limits that brings.
Outreach in several languages or markets.
An agency with several recruiters sharing sequences, with assignment rules and a manager view.
Running the standard version first is the usual path: the exceptions it logs in the first month are the scope of the custom build, with your own numbers. How custom builds work.
Frequently asked questions.
Will candidates know it is automated?
The first message references something specific they did, comes from the recruiter's real address, and stops the moment they reply — from there it is the recruiter. Generic messages get noticed; researched ones get answered.
Does it use LinkedIn?
Not in the standard version. LinkedIn steps have their own limits and tooling, so they are part of a custom build once the email version is running.
Is this compliant with anti-spam rules?
Messages are individual, professional, from a named person, with a clear way to opt out, and opt-outs are honoured everywhere. That is the standard recruiters already work to by hand; the workflow just never forgets it.
Will candidates know the outreach is automated?
They see a message from the recruiter’s address that names one specific thing they did, and the conversation continues with the recruiter. The workflow drafts and schedules; the recruiter reads every reply. A candidate who asks is told the first message was drafted with help — and the honesty rarely costs a reply.
Does candidate outreach automation use LinkedIn?
Research uses public profiles and work; sending in the standard install is email, from the recruiter’s address. LinkedIn as a sending channel, with the limits and tooling it brings, is a custom build — and the limits are the point, because a burned recruiter account is worse than a slow one.
Is this compliant with anti-spam rules?
Recruiting messages to professionals about roles are lawful in most jurisdictions when the sender is identified, the message is relevant, and opt-outs are honoured immediately; the workflow’s suppression lists and per-country rules reflect the stricter regimes. Several languages, several markets or an agency with shared sequences are custom builds.
What this blueprint is built on.
Vendor documentation the steps rely on, and the rules the guardrails are written against.
- Greenhouse — Harvest API developers.greenhouse.io/harvest.html
- NYC DCWP — Automated employment decision tools (Local Law 144) www.nyc.gov/site/dca/about/automated-employment-decision-tools.page
- Google — Email sender guidelines support.google.com/a/answer/81126