What automation is, and isn't
The real cost of doing the same task by hand isn't time, it's mistakes and forgetting. This lesson defines automation clearly, explains what it isn't, and shows which tasks are actually worth automating with concrete examples.
How many times did you do the same task by hand today? A new order came in, you sent a thank-you email. An invoice arrived, you moved it into a folder. Someone filled out a form, you copied the details into a spreadsheet by hand. Now think about it: that task was identical yesterday, and it'll be identical tomorrow.
That's exactly where automation starts, right at the repetition.
The real cost of doing it by hand
Doing a task by hand doesn't just cost you the minutes you spend on it. The real cost hides in three places: mistakes (on a tired day you write into the wrong row), forgetting (you remember that thank-you email three days later, and by then it's too late), and opportunity cost (those five minutes are five minutes you didn't spend on your actual work).
For a one-off task, none of this matters. But for something you repeat dozens of times a week, that cost compounds fast.
What automation is
Automation, put simply, is handing a rule over to a tool: "when this happens, do that." You set the rule up once, and from then on the system does the same job for you every single time.
An automatic thank-you email when a new Etsy order comes in. Incoming invoices collecting themselves into a folder. A customer who fills out a form landing both in a spreadsheet and on your email list automatically. All three follow the same logic: an event, then an automatic action.
What it isn't
It isn't magic. Automation works on tasks with clear rules. "Send a thank-you email when a new order arrives" is clear, so it automates. "Understand what the customer is thinking and reply accordingly" needs human judgment, and that's much harder to automate (not impossible, just hard).
It isn't writing code. Both Make and n8n work with visual boxes. You drag boxes and connect them to each other, you're not writing code line by line.
It isn't set-and-forget. Once you build an automation, the job isn't over. If an app you're connected to changes a field, or unexpected data shows up, the automation can break. It needs upkeep, an occasional check-in.
It doesn't make sense to automate everything. Trying to automate a task you only do once a month, and one that's slightly different every time, is a waste of effort. Building the automation itself takes time too, and you need to be sure you'll actually earn that time back.
Which tasks are worth automating
A simple test: a task that repeats at least a few times a week, whose steps are always the same, and whose rule is clear. If all three are true, that task is a candidate for automation.
Three concrete examples:
A thank-you email when a new Etsy order comes in. The event is clear (an order arrived), the action is clear (send a thank-you email), and it's the same every time.
Collecting incoming invoices into a folder. Instead of manually downloading invoices that land in your inbox and moving them to the right folder, this can flow automatically.
Adding a customer who fills out a form to both a spreadsheet and a mailing list. When someone fills out a form, their information dropping as a new row into a spreadsheet AND getting added to your email list automatically, that's one event producing two automatic results.
All three fit the same pattern: one event, then the same steps every time. In the next lesson, we'll break these steps down piece by piece, from the trigger all the way to data mapping, and see exactly how they fit inside an automation.