How automation cuts down admin work

Admin work rarely shows up on a calendar. It is not a two-hour task you can see and plan around — it is a hundred ninety-second interruptions scattered through the day.

Measure first, automate second

Before we write a single workflow, we ask the team to keep a simple log for one week. Three columns:

1. What you did — two words, not a description
2. How long it took — rounded to five minutes
3. How often it happens — daily, weekly or monthly

The result is almost always the same: two or three tasks account for 60% of the lost time. Those get automated first.

We do not automate what is easy. We automate what repeats.

The three patterns we see constantly

1. Moving data between apps

Someone reads an email, copies three fields, and pastes them into a spreadsheet. This is the cleanest win available: one webhook, one parser, one record.

2. Reminders sent by a human

If someone sends the same message every Tuesday, that does not need a person — it needs a scheduled trigger with a condition.

3. Reports assembled by hand

A monthly report stitched together from four sources is four queries and one template.

A small example

// n8n Code node: keep only the invoices waiting for approval
const pending = items.filter((item) => {
  const status = item.json.status;
  return status === 'awaiting_approval';
});

return pending.map((item) => ({
  json: {
    invoiceId: item.json.id,
    amount: item.json.total,
    supplier: item.json.supplier_name
  }
}));

Fourteen lines. They replace a filter someone was running by hand every morning.

What not to automate

Automation does not replace the decision. It clears the path up to it.

Where to start

Pick one task. The dullest one. The one nobody would defend in a meeting. Automate it within a week, measure the difference, and only then move to the next.