Why this matters

In The Toolkit, you connected your tools and built workflows you trigger by typing a message. You say "check my overdue invoices" and Claude does it. That's powerful, but it still needs you to remember to ask.

This course is about things that happen without you. While you sleep. While you're on a job. While you're at the beach. Your AI keeps working.

What we're doing

Understanding the difference between "I ask my AI to do something" and "my AI does it automatically every day." These are two very different things, and this chapter explains the gap between them.

The alarm clock analogy

Right now your AI is like a really smart employee who sits at a desk waiting for you to walk in and give them work. You say "draft a reply to that email" and they do it brilliantly. But if you don't walk in, nothing happens.

Automation is setting an alarm clock for that employee.

Every morning at 7am, they check the emails. Every Friday, they chase unpaid invoices. Every Monday, they summarise what happened last week. You never have to remember. You never have to walk in and ask. It just happens.

That's what we're building in this course.

Three types of automation

Every automation you'll ever build falls into one of three categories:

1. Time-based

"Every Monday morning, summarise my week."

These run on a schedule. Like a recurring calendar event, but instead of reminding you to do something, the AI actually does it. Same time, same task, no input from you.

2. Trigger-based

"Whenever a new email arrives from a client, add them to my client list."

These fire when something happens. A new email lands. A form gets submitted. A payment comes through. The moment that event occurs, the automation kicks in.

3. Condition-based

"If an invoice is more than 14 days overdue, draft a reminder."

These check for a specific situation and only act when the condition is true. They're like a watchdog. Always checking, only barking when something needs attention.

Why can't Claude just do this on my laptop?

This is the question everyone asks. If Claude can already draft emails and check invoices when you ask it, why can't it just do that on a schedule from your laptop?

The answer is simple: your laptop isn't always on.

Think about it. You close your laptop at 5pm. You go home. You sleep. Your laptop is off, or it's in sleep mode, or the internet disconnects. Claude can't run if the computer isn't awake and online.

For automation to work, the thing running it needs to be on 24 hours a day, 7 days a week. Rain, hail, or shine. Even when you're on holiday.

That's what a server is. It's just a computer that's always on. Not your computer. Someone else's computer, sitting in a big building full of computers, running your stuff while you sleep.

There are two main ways to use one of these always-on computers for your automations:

Option 1: Zapier (the easy way)

What it is: A website that runs your automations for you. You set them up by clicking through a visual builder. No code, no technical knowledge needed.

How it works: You tell Zapier "every morning at 7am, check my Xero for overdue invoices, ask Claude to draft a reminder, and put it in my Gmail drafts." Zapier's servers do this for you. Your laptop can be off.

Cost: Free for up to 100 tasks/month. Around A$45/month (the Professional plan) for 750 tasks. Gets expensive if you have lots of automations.

Best for: Most people. If you have 1-5 automations and don't want to touch anything technical, Zapier is your answer.

Option 2: Railway (the advanced way)

What it is: A platform where you run scripts (small programs) that do the same thing Zapier does, but cheaper. Think of it as renting your own always-on computer instead of using Zapier's.

How it works: You copy a script we give you, paste it onto Railway, tell it when to run. Same result as Zapier, but you're cutting out the middleman.

Cost: around US$5/month (about A$7). That $5 includes $5 of running costs, which easily covers small automations. If you run a lot heavier, anything above that $5 of usage is billed on top, so it's $5 to start, not a hard cap. For most small businesses it stays at $5.

Best for: People who want to save money long-term or who have 5+ automations. It's more hands-on but much cheaper.

Key terms in plain English

Before we go further, here are some words you'll see in this course. No jargon. Just plain explanations.

Word	What it actually means
Server	A computer that's always on, always connected to the internet. Not yours. Runs your stuff while you sleep.
Cloud	Same as "server." Just a marketing word. "In the cloud" = "on someone else's computer."
Script	A small set of instructions (like a recipe) written in a programming language. You don't write them, you copy ours.
Deploy	Putting your script onto a server so it can run. Like uploading a file to Google Drive, but for code.
Cron	A schedule for when something runs. "Cron job" = a task that runs at a set time. Like setting an alarm.
Environment variable	A setting your script needs, like a password or connection key. Stored separately so it's secure.
API	A way for two apps to talk to each other. When Claude checks your Xero, it's using Xero's API. Connectors (MCP) use APIs under the hood.
Task (Zapier)	One step in a Zapier automation. Checking one invoice = 1 task. Drafting one email = 1 task. They add up. (One exception: each Zapier MCP tool call uses 2 tasks.)

What you just learned

• Automation means things that happen without you asking
• There are three types: time-based (on a schedule), trigger-based (when something happens), and condition-based (when a condition is met)
• Zapier is the tool you'll use to build automations
• You already know Zapier from Chapter 10, so this isn't starting from scratch

Try it yourself

• Think of 3 things in your business that happen on a schedule (weekly reports, invoice reminders, stock checks)
• Think of 2 things that should happen automatically when something else happens (new email, new booking, payment received)
• Write these down in your notes. You'll build at least two of them in the next few chapters.

Mark chapter as complete