Starting point
An onboarding process that runs over email tends to look the same everywhere: the signed contract comes back, HR emails IT with the start date, IT orders hardware, and the manager often finds out just days before someone starts. Every single step is mundane. The problem is the chain: seven to eight people are typically involved in one onboarding, and every handover is a point where something can be forgotten.
In practice, this only becomes visible once it breaks: a new colleague without a laptop on day one, a welcome email that never went out because the responsible person was on leave. None of this comes from a lack of care — it comes from the fact that a process with seven participants is not a reliable system, it is a chain of reminders.
Approach
The first step is not the screen, it is paper: what triggers the process, which five or six data fields does it actually need, who receives which message, and where does a human have to decide instead of the machine running on its own. This sketch comes before any workflow configuration, because it has to be aligned with IT and the works council later — and because a cleanly sketched process stands in n8n within hours, an unclear one takes weeks.
n8n then reads only the fields the process actually needs: name, start date, department, manager, location. The signed contract itself is never touched or forwarded, it stays in the personnel file. From these fields, an IT ticket with the start date, a calendar entry for the manager's welcome meeting, a first-day task list, and, three days before the start, the draft of the welcome email are created automatically.
Before the welcome email is sent, there is an approval step: HR sees the draft and either sends it or holds it back. This is not a technical detail — it is the point where the works council typically has a say, because a workflow that automatically triggers actions is a technical system for the purposes of German co-determination law. The approval step is the proof that a human always makes the final call, not the automation alone.
Step by step
Document the existing email chain: who is involved, which data goes where, where it breaks down most often.
Define trigger, data fields, recipients and approval points together with HR, IT and, where one exists, the works council.
Connect trigger, IT ticket creation, calendar entry, task list and welcome email draft as nodes, with an approval step before sending.
Run the complete process once with made-up test data before the first real case goes through it.
Go live with the next real onboarding, HR accompanies the first approval closely.
Outcome
After the first complete run, the process operates without manual intervention up to the approval step before the welcome email. The typical time savings are in the coordination steps, not in the empathy: the manager learns the start date automatically instead of having to ask, and HR no longer has to chase whether the IT ticket was processed.
The approval step stays in place permanently, not just at the start. That is intentional: an automated process that sends messages to the outside world should always be stoppable by a human when something changes at short notice — a shifted start date is the most common reason.
Prerequisites
- n8n instance in placeSelf-hosted or on a private cloud instance, with access limited to HR and IT.
- Structured HR dataName, start date, department, manager, location in a system n8n can read from.
- A ticketing system or inbox for ITSo the IT ticket can be created automatically, whether via API or email.
writes this from own n8n projects in HR teams, composited and without client names. Mehr zum Autor