← Back to directory
HR & Recruiting Medium to set up AI workflow Orchestrate/Approve

Recruitment Rejection Email Sender

Source reviewed Updated 2026-07-07

Every day at 18:00 IST, the agent sends personalized rejection emails to candidates marked as rejected in your Google Sheet.

What it does

You save time by automatically sending personalized rejection emails to candidates marked as rejected in your Google Sheet every day at 18:00 IST. This process uses Gmail templates while preventing duplicates through timestamp tracking and dry run modes for safe testing.

Step by step

  1. Configure an n8n cron node to trigger the workflow at a specific end-of-day time.
  2. Set up a Google Sheets node with read-only access to fetch rows from the candidate tracking sheet.
  3. Implement a code node using JavaScript to filter rows where the status column equals 'Rejected' and check for existing sent timestamps.

Where the LLM does the work

  • Generate personalized rejection email body text that maintains empathy while clearly stating the decision based on candidate role history.
  • Draft variations of the subject line to ensure high deliverability and appropriate tone for different seniority levels.
  • Refine the Gmail template variables to ensure dynamic fields like candidate name and job title are inserted correctly without syntax errors.

Watch out for

Gmail API quotas can be exceeded during bulk sends, so add a sleep node between batches to stay within daily limits.
Template variable mismatches will cause empty fields in emails, so validate all placeholder keys against the actual column headers in your source data.
Sensitive candidate data might leak if error logs are exposed, so configure n8n to mask personal information in any debug output or webhook responses.

Tools that fit

n8n Service Workflow orchestration and automation logic
Google Sheets Service Reading candidate status and details
Gmail Service Sending personalized rejection emails via SMTP

The agent brief

Everything your agent needs, including the gotchas. Copy it and go.
agent-brief.md
You are helping me build the following AI agent workflow.

## Goal
Recruitment Rejection Email Sender: Every day at 18:00 IST, the agent sends personalized rejection emails to candidates marked as rejected in your Google Sheet.

## Specification
- What it does: You save time by automatically sending personalized rejection emails to candidates marked as rejected in your Google Sheet every day at 18:00 IST. This process uses Gmail templates while preventing duplicates through timestamp tracking and dry run modes for safe testing.
- Trigger: On a schedule (Scheduled ยท daily 18:00 IST)
- Autonomy: Fully hands-off
- Expected setup effort: about an afternoon
- Tools/services involved:
  - n8n: Workflow orchestration and automation logic
  - Google Sheets: Reading candidate status and details
  - Gmail: Sending personalized rejection emails via SMTP

## Known pitfalls, handle each one explicitly in your implementation
1. Gmail API quotas can be exceeded during bulk sends, so add a sleep node between batches to stay within daily limits.
2. Template variable mismatches will cause empty fields in emails, so validate all placeholder keys against the actual column headers in your source data.
3. Sensitive candidate data might leak if error logs are exposed, so configure n8n to mask personal information in any debug output or webhook responses.

## Reference implementation
https://n8n.io/workflows/7766 (workflow template)
Fetch and inspect this before building. If it matches my stack, adapt it;
if not, rebuild the pattern with my tools.

## Process requirements
1. Before building: ask me which of the listed tools I actually use and
   what my platform is (n8n / Make / code / other). Do not assume.
2. Adapt the pattern to my answers; do not force the reference stack.
3. Address every pitfall above; tell me how you handled each.
4. Provide a test plan I can run before letting this touch real data.
5. Ask before any step that sends messages, modifies data, or spends money.

Source: https://usecasesforagents.com/use-case/automated-recruitment-rejection-email-sender/ via usecasesforagents.com

Frequently asked questions

Can I use a different Automation Platform than n8n?

Yes. n8n is only the example automation platform in this recipe. The same flow works with Home Assistant. Swap the automation platform connection and keep the rest of the setup as written.

Want this running in your business?

This is what I do. I design and build AI agents like this one, and keep them running. If you want it set up for your team instead of doing it yourself, get in touch.
Get in touch →

Who it's for

Built for HR and recruiting teams who need a repeatable first pass, not a one-off.

Seen in the wild

← Back to directory