Contents6
When a company decides to automate, every department puts itself forward. Accounting is buried in reminders, sales is losing contacts, HR is retyping forms, support is chasing deadlines. Everyone is right, and you cannot do everything at once. The choice of the first department matters more than it seems: a successful first project makes the others want one, a first project that gets stuck discourages people for a long time.
This article gives a grid for choosing. It belongs to the cluster n8n workflows: what each department can automate, which then details the workflows of each department.
In short
Frequency: a task that comes back every day or every week.
Trigger: a clear event, readable in a piece of software.
Cost of a mistake: low, or easy to put right.
Champion: someone in the department who wants it to work.
The process that hurts the most is not necessarily the right first choice.
The four criteria
- Frequency.
A task that comes back every day pays off quickly and is checked quickly. A quarterly task brings little, and you wait three months to know whether the workflow works.
- The trigger.
“An invoice falls due”, “a form is sent”: that is clear. “When the customer seems unhappy” is not.
- The cost of a mistake.
A reminder sent a day too early can be put right. A transfer sent to the wrong supplier, much less so.
- The champion.
Someone in the department who knows the task, wants to get rid of it and will take the time to test.
The second criterion is quick to check: the n8n documentation lists its triggers, at a set time, on a form, on a message received or on a change in a piece of software. If the task starts on none of them, it is not ready. The fourth criterion is the one most often forgotten, and the most decisive. A workflow built for a department that did not want it is worked around or ignored. A workflow championed by someone in the department is corrected, improved and defended.
Applying the grid, department by department
Often good first candidates
Accounting: unpaid invoice reminders, expense reports
Support: deadline alerts, tickets without an owner
HR: leave and absences
Often best kept for later
Commissions, as long as the rules are not written down
Cash, as long as the bank data is not accessible
Any process that crosses five departments
Unpaid invoice reminders almost always tick all four boxes: daily, triggered by a date, easy to put right, and the accountant is rarely attached to this task. Support deadline alerts too. On the other hand, commissions first require writing rules that often exist only in one person’s head: a good second project, rarely a good first one.
The trap of the process that hurts the most
The temptation is to start with what causes the most pain. It is often a long process, crossing several departments, with many exceptions: the full chain from order to delivery, for example. The potential gain is large, but so is the project. Several managers have to agree, special cases have to be mapped, five tools have to be connected. The first result arrives late, and confidence wears thin while you wait.
It is better to start with one piece. In the chain from order to delivery, the shipping updates sent to the customer are a self-contained piece, which pays off on its own and prepares the rest.
Measure before you start
Before building, write down three figures for the chosen task, estimated with the department: how many times it comes back each week, how long it takes, and how many errors or omissions it produces. A month after going live, take the same readings again. It is not a study, it is an honest comparison between before and after, which helps you make the case for the next project.
The article 10 automations for a 50-person company gives a broader list of ideas, useful for building the queue of next projects.
After the first one
The first successful workflow has a useful effect: the other departments come with their requests. This is the moment to set a simple rule, every new workflow has a named owner, otherwise you build a collection of automations that nobody watches.
To choose your first department and build the workflow that will convince the others, our n8n automation offer starts with a survey of the tasks repeated in each department.
Frequently asked questions
Should you start with management?
Not necessarily. Management is a good sponsor, but its tasks are often less frequent and more varied than those of the operational departments. A first workflow in an operational department gives a visible result sooner. Management can benefit afterwards, for example with an approval circuit or a cash alert, once the method is well established.
Can you launch several departments at the same time?
It is possible with a dedicated team, risky without one. Each workflow needs time from the department concerned to describe the task and to test. By launching several departments at once, you spread attention thin and delay every result. Two workflows properly finished are worth more than five half done.
How long does a first workflow take?
For a well-chosen task, from a few days to a few weeks, depending on the number of tools to connect and on how available the department is for testing. The longest part is not building, but describing the task and its exceptions precisely. A workflow that needs months is a sign of a first choice that was too ambitious.
Sources
- Official n8n documentation (new tab)docs.n8n.io
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 guide10 min
10 automations for a 50-person company
Ten flows that take copy-and-paste off a team of 20 to 500 people, from the incoming enquiry to the unpaid invoice reminder. For each one: what it prevents, what stays human, and the step where AI helps, when it helps.
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.