Contents6
In many companies, a leave request follows a vague path. The employee sends an email to their manager, who replies “ok” from their phone. HR finds out at the end of the month, or does not find out at all. The team calendar is never up to date, and two people from the same department end up away the same week.
None of this is serious on its own. Together, it means wrong schedules, disputed balances and hours spent working out who was where. This article is part of the n8n workflows: what each department can automate series, human resources section.
In short
A single entry point for requests: a form.
The balance is checked before the request goes to the manager.
The manager approves in one click, seeing who else is away.
Approval updates the calendar, the balance and the payroll export at the same time.
The rules (notice period, blocked periods) are written once.
Why the email circuit does not hold
Email works for asking. It does not work for tracking. A request approved by email exists only in two inboxes, and every other tool (calendar, payroll, schedule) has to be updated by hand. The smallest oversight creates a gap, and the gap is found at the worst moment: a customer waiting for someone who is away, a wrong leave balance on the payslip.
The legal framework adds a constraint. Service Public sets out the rules on paid leave for private sector employees in France, including how leave is earned, the period when it is taken and the order of departures set by the employer. A recorded circuit lets you show what was requested, approved or refused, and when.
The path of a request
A leave request in n8n
- The request
The employee fills in a short form, with dates and type of absence.
- The check
The workflow checks the balance and the blocked periods.
- The approval
The manager receives the request, with the absences already planned in the team.
- The update
Team calendar, balance and payroll export change at the same time.
The manager approves from a link or a button in their messaging tool. The n8n Wait node lets the workflow wait for that answer, then pick up where it stopped. With no answer after a few days, it reminds the manager, then alerts HR.
The rules, written once
What the workflow applies
The minimum notice period
The periods when leave is blocked
The maximum number of people away per team
What the manager decides
Two requests for the same week
An exception for personal reasons
A postponement when workload is unexpected
The workflow applies the rule, but it does not decide. When two employees ask for the same week, it flags it to the manager, who decides on human grounds: length of service, family constraints, what was granted last year. This is the kind of decision a machine would make badly, and that an employee would accept badly from a machine.
What everyone gains
The employee sees where their request stands, without chasing. The manager sees the team at a glance before approving. HR no longer copies anything and has a clean history. Payroll receives absences on a fixed date, instead of a list pieced together at the end of the month.
The same pattern works for other internal requests: remote work, training, equipment. It looks like the one for management approvals, with a shorter circuit.
HR software or workflow?
Time management software does all of this, with its screens and its subscription. It is the right choice when the company also wants timesheets, detailed schedules and a full employee portal. The n8n workflow fits when the need is limited to leave and absences, with existing tools (shared calendar, payroll software) that you want to connect without adding another one. You can also start with the workflow, then move to software when the need grows: the data stays yours.
To set up this circuit on your calendar and payroll software, our n8n automation offer starts from your real rules and the cases that cause problems today.
Frequently asked questions
Can n8n calculate the leave balance?
It can, but it is better to read it from the payroll software, which is the reference. The workflow queries the balance before sending the request to the manager and updates it after approval, without calculating entitlements itself. This avoids two calculations that drift apart, a classic source of disputes at the end of the year.
What happens if the manager is away?
The workflow can pass the request to a named deputy after a set time, or straight to HR. This rule is decided at the start: who approves when the manager is on leave, and after how many days. Without it, requests get stuck, and the employee does not know who to turn to.
Do employees have to learn a new tool?
No, that is the point of the circuit. The employee fills in a short form, the manager clicks a button received by email or in their messaging tool. Nobody has an account to create or a screen to learn. Only HR looks at the full tracking, in a table or in the tool it already uses.
Sources
- Congés payés du salarié dans le secteur privé, Service Public (new tab)service-public.fr
- Wait, n8n documentation (new tab)docs.n8n.io
Congés payés du salarié dans le secteur privé, Service Public
Read on service-public.fr(new tab)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 guide4 min
Job applications: an n8n workflow from CV to interview
Applications arrive through five channels and get lost in inboxes. An n8n workflow brings them together, replies to every candidate and prepares the screening, without ever deciding for the recruiter.
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.