Contents6
In a company of a few dozen people, every department has its copy and paste. The accountant copies due dates into a spreadsheet to chase payments, HR forwards applications by hand, support watches for tickets that are getting old, the buyer calls a supplier whose delivery never arrived. None of these tasks is difficult. All of them come back every week, and all of them depend on someone remembering.
n8n is the tool that connects this software so that information moves without being typed again. This guide is the entry point of the “n8n workflows by department” cluster: it goes round the departments, says what can be automated in each one and points to the articles that detail each workflow. The overall view of automation, tools included, is in our guide to automating your business processes.
In short
A good workflow starts from a repeated task, triggered by a clear event (an invoice falling due, a form sent, a status that changes).
Each department has three or four workflows worth the effort; beyond that, the gain falls and the maintenance rises.
People keep the decision: the workflow prepares, alerts, reminds, and leaves anything that commits the company to be approved.
A workflow without a named owner ends up failing silently.
Start with a single department, measure, then extend.
What an n8n workflow is, in business terms
A workflow is a series of steps that starts on a trigger: a set time, a form, a message received, a change in a piece of software. According to the n8n documentation, these triggers and the steps that follow connect to hundreds of applications, and to all the others through their API. For a department, that means one simple thing: what used to live in someone’s head (“I’ll chase on Tuesday”) becomes a written rule that runs, with a record of each run.
The gain is not only time. It is regularity: the reminder goes out on the planned day even when the accountant is on holiday, and you know how many files are waiting.
Department by department: what can be automated
What the workflow does well
Remind, chase, pass on at the right moment
Gather scattered information into a single message
Alert when a deadline is about to be missed
What the department keeps
Deciding on a commercial gesture or a hire
Talking to an unhappy customer
Approving a purchase or a contract
Accounting. The three most profitable projects are unpaid invoice reminders, expense reports and preparing the monthly close. Reading supplier invoices has its own article: automating reading and matching.
Sales. After the move from quote to invoice, already covered in From signed quote to paid invoice, there remain contract renewals and calculating commissions.
Human resources. Sorting job applications, approving leave and an employee leaving, which is the moment when someone forgets to remove an access.
Support. Sorting tickets with AI is covered in Automating customer support. This cluster adds the alert before a response deadline is missed and the satisfaction survey sent at the right moment.
Purchasing and logistics. Purchase requests and their approval, spotting late suppliers and the shipping updates sent to the customer.
Marketing. Competitor monitoring and following up people registered for a webinar or a trade show.
Management. The approval and signature circuit and the cash alert.
In what order to go about it
- List.
With each department, the tasks repeated every week, and the time they take according to the people who do them.
- Choose.
The most frequent task, with the clearest trigger, where a mistake costs little.
- Build.
A short workflow, with a record of each run and an alert if it fails.
- Name.
An owner, who knows how to read it and who receives the alert.
- Measure, then extend.
A month later, compare with the starting list.
Choosing the first department has its own article: which department to automate first. The question of who looks after each workflow, often forgotten, is just as important.
What makes a department workflow fail
Three causes come up again and again. The first is a workflow built for a task the department no longer does, or does differently: you automate the written version of a process, not the real one. The second is the lack of an alert: an API changes, the workflow stops, and nobody notices for weeks. Our article on monitoring n8n workflows details the safeguards. The third is too much ambition: a workflow that handles every special case becomes unreadable, whereas three cases out of four are often enough, with the fourth staying manual.
What n8n changes compared with Make or Zapier
The principle is the same in all three tools. n8n stands out because you can host it yourself, which keeps the departments’ data (HR and accounting first) on a server you control. The full comparison is in n8n, Make or Zapier: which to choose.
To go from the list to workflows in production, our n8n automation offer starts from your departments’ tasks, builds the first workflows with their monitoring and trains the person who will look after them.
Frequently asked questions
How many workflows does each department need?
Three or four are usually enough to cover most of the time lost. Beyond that, each new workflow brings less and needs as much maintenance. Four monitored workflows, with an owner, are better than fifteen that nobody looks at. You add one when a department comes back with a specific task, not to fill a list.
Do these workflows need AI?
Not always. Most department workflows are rules: a date, a status, an amount. AI helps when free text has to be read, such as an email, a CV or a scanned invoice. In other cases, a simple rule is more reliable, cheaper and easier to check than a language model.
Can a department build its workflows on its own?
It can change them, but rarely design solid ones without help at the start. The most effective approach is to build the first ones with a provider, while training the person in the department who will look after them. They will then be able to adjust a delay or a recipient, and ask for help only for a change of structure.
Sources
- Official n8n documentation (new tab)docs.n8n.io
Jim · founder of Brain Plus AI
Also in n8n workflows by department
Choose and price4 min
Which department should you automate first with n8n?
Accounting, sales, HR, support: every department has good reasons to go first. Four simple criteria help you choose, and avoid the first project that discourages everyone.
Practical guide8 min The topic guide
Automating business processes: the guide
What to automate first, with which tool, where AI belongs and how to avoid silent failures: the entry guide to our Automation and bots section, with a link to every article that goes deeper.
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.