What is automation?
Automation is having a computer perform a rule-based, repeating task without human intervention. In business the most common form is workflow automation: an event (a new email, a form, a time of day) triggers a chain, data is transformed and written to a target system. It's built with visual tools (n8n) or terminal scripts, and both can run on your own server.
- Rule-based, repeating tasks can be automated
- A workflow: trigger → condition → action → target
- n8n is visual, scripts are flexible; most setups use both
- Automation removes repetition, not people
What is automation?
Automation is having a computer carry out a rule-based, repeating task without needing a person each time. A robot arm in a factory is automation, and so is a small script that runs at 3am and produces a sales report.
The word sounds big, so many businesses assume it isn't for them. But a typical automation project looks like this: a bookkeeper copies orders from email into a spreadsheet every morning; it takes ten minutes a day, roughly four hours a month, and it's easy to get wrong. Automation takes those ten minutes to zero.
Which tasks can be automated?
Three questions tell you whether a task is a good candidate:
- Is the rule clear? "Add emails with ORDER in the subject to this sheet" is clear. "Decide based on what the customer meant" is not.
- Does it repeat? Automating something done monthly rarely pays off; automating something done several times a day pays off quickly.
- Can the result be checked? If you can see at a glance whether the output is right, you can trust the automation.
Three yeses means the task is a good fit. One no usually means the whole task isn't automatable — but its repeating part is.
The most common business automations
- Data transfer: Moving information from an email or form into a sheet, CRM or accounting system.
- Reporting: Producing yesterday's sales, stock or attendance report each morning and sending it out.
- File handling: Naming and filing incoming PDFs, batch-resizing images, merging invoices.
- Notifications: Messaging the right person when stock drops below a level, a payment is late or a new request arrives.
- Backups: Backing up databases and files every night, and verifying the backup.
How is a workflow put together?
Almost every workflow has the same four parts:
| Part | What it does | Example |
|---|---|---|
| Trigger | The event that starts the flow | New email, form submission, 3am |
| Condition | Chooses which records continue | Subject contains "ORDER" |
| Action | Transforms or enriches the data | Format the date, parse the amount |
| Target | Writes the result somewhere | Append to sheet, send a message |
n8n or scripts — what's the difference?
n8n is a source-available, fair-code licensed tool for building workflows visually. Each step sits on screen as a box, so you don't need to read code to understand it, and there are ready-made connectors for common services. It can be self-hosted.
Terminal scripts (Bash, Python) run directly on a machine. They're more flexible for file handling, batch conversion, working with local folders and scheduled jobs. There's no visual interface, but there's no ceiling either.
In practice most setups use both: cross-system flows in n8n, and the heavy machine-side work in scripts.
Does automation take people's jobs?
What we see in practice is that automation removes the boring part of a job, not the job. When someone stops copying orders into a spreadsheet, they spend that time talking to customers and catching mistakes instead. The tasks best suited to automation are the ones nobody enjoys anyway.
Good automation is invisible. Nobody mentions it while it works — you only learn how many hours it saved when it stops.
Frequently asked questions
Does automation make sense for a small business?
It often helps small businesses most, because the same person handles sales, accounting and operations. A single flow saving half an hour a day adds up to ten hours a month.
Do we need to buy new software?
Usually not. Automation connects the systems you already have — your email, spreadsheets, accounting and messaging apps stay where they are.
Which task should we start with?
The one that repeats most and annoys you most. Note how many times you do each task over a week; the list usually makes itself obvious.
Will we become dependent on you afterwards?
You shouldn't. In visual tools like n8n the flows are readable, so your team can make small changes; for scripts, the source code and documentation are handed to you.
