Contents7
Monday, 9 a.m. The new hire is there, smiling; their laptop has not arrived, their mailbox does not exist, and nobody knows who is supposed to give them access to the CRM. They spend their first morning waiting. Nothing serious, but it is the first impression they keep of the company, and a whole team loses time catching up on what could have been ready. This guide from our section on process automation and business bots lists what automation can prepare before the arrival, and what rightly stays with people.
In short
The first day is prepared before the arrival, from a single event: the employee record approved by HR.
Accounts, role-based access, equipment, reminders and first-week meetings are automated without AI.
The welcome, goals and follow-up stay with the manager and HR.
Access created automatically is removed the same way on departure: that is the strongest security argument.
A written, up-to-date list is worth more than a tool bought before the process has been described.
Why the first day is prepared before the arrival
A new hire involves more people than you think: HR for the contract and formalities, IT for accounts and the workstation, facilities for the access card and the desk, the manager for the schedule and the first files. Each waits for information from another, and it is in these handoffs that things get forgotten.
Some steps allow no delay. In France, the pre-hiring declaration (DPAE) is, according to France Travail, “mandatory before any hiring” and is made with a single body, the Urssaf. Automation does not replace the person who files it, but it can make sure nobody forgets it has to be done, on the right date.
What can be automated: everything starts from one event
The most reliable trigger is simple: the new employee’s record, approved by HR in their tool, with role, team, manager and start date. Everything else follows from it.
From the approved record to a ready first day
- The record
HR approves role, team, manager and start date.
- The accounts
Mailbox, tools and access groups by role.
- The equipment
The request goes out with the date, the access card is prepared.
- The week
Welcome meetings land in the calendars.
In practice, an automation can:
- create the accounts: mailbox, chat tool, CRM, business tool, each with the rights of the role and no more;
- put the employee in the right groups: a salesperson joins the sales group and inherits its access, rather than receiving access granted one item at a time;
- open the requests for equipment and building access, with the start date and the person responsible;
- prepare the documents to sign and send them for electronic signature;
- book the first week’s meetings: welcome by the manager, team introduction, end-of-week check-in;
- remind each person responsible of their tasks, on the right date, and chase those that are not moving.
What does not need AI (almost everything)
All these steps follow rules: this role gets this access, this start date gets this schedule. The same input always produces the same result, which is exactly what you want from a process that touches access rights. Our guide to automation without AI, when a rule is enough explains why this is the right default.
AI finds its place alongside, not in creating access: answering the new hire’s questions from your internal documents, as an assistant that answers with your documents does, or preparing a first draft of a welcome message that the manager reviews and signs.
What stays human
Automation takes chasing other departments off HR’s plate, not the relationship with the employee. The contract, the interview, the probation follow-up and personal questions remain their job. The manager welcomes, explains goals and introduces the team; a colleague acting as buddy answers the questions people do not dare ask their manager. No workflow replaces lunch on the first day.
Key takeaway
Good onboarding automation shows in what people no longer have to do: chase an access card, remind IT, copy the same record into three tools. The time freed goes to the welcome.
The departure is prepared on the day of arrival
This is the strongest argument, and the least visible. ANSSI, the French national cybersecurity agency, devotes a whole measure of its guideline for a healthy information system to arrivals and departures:
It is essential that all of the rights granted to an individual are revoked when he or she leaves or changes position.
The guide asks for these procedures to be defined together with human resources, and to cover at least accounts and mailboxes, role-related rights, access cards and keys, equipment handed out and shared passwords. When access was granted by an automation, based on the role, the list of what to remove already exists: the departure becomes the same process in reverse. When it was granted by hand, request after request, nobody really knows any more what needs cutting.
From the field
We apply this rule to our own AI agents, which are “new arrivals” like any other: each has its own rights, limited to what it needs, the access key is added in transit by the network layer and never placed in its environment, and every call leaves a trace. Removing an agent means removing one line, not searching for where its keys were copied. Our guide to the secrets vault for AI describes the setup.
Where to start
- Write the list.
Every task of an arrival, with its owner and deadline.
- Define the profiles.
For each role, the tools and rights that go with it.
- Choose the trigger.
The record approved by HR, in the tool where it already exists.
- Automate the most repetitive first.
Accounts and reminders first, the rest next.
- Write the departure at the same time.
The same list in reverse, tested on the next departure.
The choice of tool comes after the list: our comparison of n8n, Make or Zapier for a small business helps decide, and our n8n automation, with or without AI starts from the task observed with the person who does it today. If an HR or business tool has no API, see the six ways into software without an API.
The other articles in the section: automated supplier invoices, reports without copy-and-paste, WhatsApp and website bots, AI voice agents on the phone, customer support sorted by AI, monitoring n8n workflows, the n8n licence and AI and young people’s first jobs, which raises the question of training juniors.
Frequently asked questions
What is employee onboarding?
It is everything that accompanies a new employee’s arrival: formalities, workstation, access, welcome and the first weeks. One part is administrative and repeats with every arrival, and that is the part you automate; the other is human, and stays with the manager and HR.
Which onboarding tasks should be automated first?
Those that repeat identically and block the first day when forgotten: creating accounts and the mailbox, granting access by role, requesting equipment and reminding the people responsible. They follow simple rules, need no AI, and are also the ones whose reverse list makes departures safe.
Do you need HR software to automate onboarding?
Not necessarily. Above all you need a place where the employee record is approved, to act as the trigger, and a written list of tasks. An orchestrator like n8n can connect the existing HR tool, the mailbox and the other applications. Dedicated HR software is justified when hires are frequent or processes complex.
How can you be sure to remove all access when an employee leaves?
By granting access through groups tied to the role, and creating it with the same automation that will remove it. The list of what to cut then exists from day one. ANSSI recommends defining these arrival and departure procedures with human resources, and revoking all rights on departure.
Sources
- France Travail (new tab)francetravail.fr
- Guideline for a healthy information system (new tab)messervices.cyber.gouv.fr
Jim · founder of Brain Plus AI
Also in automation and bots
Choose and price9 min
Automation without AI: when a rule is enough
Not every automation needs AI. A fixed rule costs less and always gives the same result: here is how to spot the steps where AI really pays off, and those where it only adds cost.
Practical guide6 min
Supplier invoices: automating reading and matching
A supplier invoice goes through three steps: reading it, matching it against what was ordered and received, then approving it before payment. What can be automated at each step, where AI really helps, and what stays with the accountant.
Choose and price8 min
n8n, Make or Zapier: which to choose for an SME?
All three tools connect your applications without heavy development, but they do not charge for the same thing and do not give you the same freedom. This comparison for decision-makers looks at the billing unit, hosting, licence and who maintains it the day it breaks.