Contents6
An open position in a company of fifty people quickly produces a familiar mess. Applications come in through the website, two job boards, LinkedIn, and an email forwarded by a colleague. The manager reads some, HR reads others, and a few candidates never get a reply. That last point is the most costly: an ignored candidate talks about it, and the employer brand suffers.
An n8n workflow does not recruit. It sorts, replies and prepares, so that the recruiter’s time goes into interviews. This article is part of the n8n workflows: what each department can automate series, human resources section.
In short
All applications arrive in the same place, whatever the channel.
Every candidate gets an acknowledgement, then an answer, positive or not.
The recruiter reads a consistent summary instead of scattered formats.
Interviews are booked through a link to available slots, without back and forth emails.
The decision to keep or reject a candidate stays human, and the data has a deletion date.
The real problem: scattering
Recruitment suffers less from a lack of candidates than from scattered applications. Each channel has its own format, its own inbox, its own notification. With no central point, nobody knows how many applications have come in, or which ones are waiting for a reply.
The first gain from a workflow is therefore a single table. The website sends the form, job boards send an email or offer an API, and the recruitment inbox receives the rest. n8n reads each of these inputs, pulls out the name, the position, the CV and the source, and creates a line. The recruiter opens one screen.
The journey of an application
An application in n8n
- Arrival
Website, job board or email, the workflow captures the application.
- The summary
It files the CV and creates a line in the tracker for the position.
- Screening
The recruiter reads the summary and decides what happens next.
- The answer
Depending on the decision, the workflow sends the invitation or a polite rejection.
The screening step is highlighted on purpose: it is the only one that is not automated. You can ask a language model to summarise a CV or check that it mentions a required qualification, as long as the recruiter always sees the full document and the summary is a reading aid, not a filter. Rejecting a candidate on an algorithm’s reading alone raises a question of law and fairness, which the article Automated decisions: can AI decide on its own? covers in detail.
Replying to everyone
- The acknowledgement.
It goes out within the hour, with the planned recruitment timeline.
- The positive answer.
A link to the manager’s slots, who sets their own availability.
- The rejection.
A polite message, prepared in advance, which the recruiter sends in one click.
- Closing the position.
A message to those still waiting when the position is filled.
A one click rejection changes a lot. Without it, the negative answer is the task you put off, then forget. With it, every candidate gets an answer, and HR does not spend Friday afternoon writing messages.
Data retention, settled from the start
A CV contains personal data. The CNIL publishes its recommendations on recruitment, including informing the candidate and how long an application can be kept. The workflow can apply these rules better than a person: it records the date of last activity on each application, and deletes or anonymises those that go past the set period, after an optional message asking the candidate whether they want to stay in the talent pool.
It is also a reason to host n8n on your own server: CVs do not pass through one more third party service.
After recruitment
Recruitment ends with someone joining. The workflow that followed the application can hand over to the onboarding one: accounts, equipment, first day. That process has its own article, Employee onboarding: what to automate for day one. And at the other end of a career, there is the employee leaving, where access is cut off.
To bring your recruitment channels into a single tracker, with replies and data retention, our n8n automation offer starts from your open positions and your current tools.
Frequently asked questions
Do you need recruitment software as well as n8n?
Not necessarily. For a few hires a year, a shared table fed by n8n is enough. Beyond that, an applicant tracking system brings views per position and statistics. n8n then plugs into it to capture the channels it does not read and to send the messages. The choice depends on volume, not on company size.
Can AI shortlist CVs?
You can ask it to summarise or spot a piece of information, not to decide on its own. The recruiter must see each full application and stay responsible for the choice. An unchecked automatic shortlist risks rejecting good profiles over a detail of form, and raises legal questions about automated decisions. The tool helps you read, it does not sort for you.
How do you handle speculative applications?
They enter the same process, under a “speculative” position. The candidate receives an acknowledgement that says clearly what will happen, and how long their application will be kept. The workflow can then suggest these profiles to the recruiter when a similar position opens, provided the candidate has agreed to stay in the talent pool.
Sources
Jim · founder of Brain Plus AI
Also in n8n workflows by department

Practical guide5 min The topic guide
n8n workflows: what each department can automate
Accounting, sales, HR, support, purchasing, marketing, logistics, management: every department has tasks that travel from one tool to another. Here, department by department, are the n8n workflows that save time, and those that are not worth the effort.

Practical guide6 min
Employee onboarding: what to automate for day one
An employee's first day is decided before they arrive: accounts created, equipment ready, access granted according to their role. What automation can prepare, what stays with the manager and HR, and why the departure should be prepared at the same time.

Practical guide4 min
An employee leaving: removing access without missing any
When an employee leaves, their accounts often stay open for weeks. An n8n workflow runs the exit checklist, removes access at the right moment and keeps a record of each step.
