What Automations Actually Are
What scheduled tasks change.
Scheduled tasks fire when you're not watching the chat. Connected calendars get read without you opening them. Connected inboxes get scanned on a clock you set. This is the first time Claude reaches into your accounts on its own.
Before you set up a single scheduled task, you're going to learn what's actually happening behind the scenes and what you're agreeing to when you turn on a connector.
What a scheduled task actually is: and what it definitely isn't.
The phrase "AI automation" has been doing a lot of misleading work on the internet for the last couple of years. Before we go further, here's the precise version of what a scheduled task is, and the precise version of what it isn't. The mismatch is where most students either over-trust this thing or skip it entirely.
What it IS
A saved prompt that fires on a schedule you set. Sunday 6pm. Daily 7:30am. First of the month. Whatever you pick.
Runs on Anthropic's servers, not your laptop: your laptop can be closed, your phone in your pocket, you in the shower. The task fires anyway and the output shows up in your Claude chat as a new message.
How it reaches your stuff
Through connectors:explicit, named, two-click-revocable bridges to specific accounts. For Module 9 we use exactly two: calendar (Google, Outlook, or Apple via iCloud) and email (Gmail or Outlook).
Read-only by default. Claude can see your events, not edit your calendar. Can search your inbox, not send mail. Can be turned off in two clicks (Screen 4).
What it ISN'T
Not auto-logging into your school's LMS. Not opening Common App and submitting things. Not doing your homework while you sleep. Not posting on your behalf. Not buying things. Not making decisions.
The audit habit: three checks, plus the disconnect drill.
Run these three checks now, before you set up any tasks. Then run them again in the first week of every new semester.
Check 1 · Calendars
Open Settings → Connectors → Calendar. If you have multiple calendars (school, personal, family, partner's shared, club's shared), look at which ones are toggled on for Claude.
Most students need school + one personal with work shifts and exams.
Check 2 · Email
Settings → Connectors → Gmail (or Outlook). Confirm it's off if you didn't set up an App Deadline Tracker. On only if you did.
Check 3 · Frontmost-of-mind
For each connector currently on, finish this sentence out loud: "This is on so that Claude can do [specific task name]."
Calendar → "so Claude can run my Sunday Reset." Email → "so Claude can flag application deadlines from my tracker doc on the 1st." If you can't fill in the blank with a specific task name, turn the connector off. Default is off; on has to earn its slot every time you do this audit.
The two-click disconnect drill
Pick any connector you have on. Settings → Connectors → that connector → Disconnect. Confirm. It's off. Reconnect (one more click + re-auth). It's back on.
Do this once now. The point isn't to leave it disconnected: the point is to know exactly where the off switch is, so future-you can find it fast when needed.
The every-semester re-audit
First week of every new term, run the same four-step check. Pause any task tied to last semester's classes (Pre-Exam Watch especially: the exam tags are gone). Update Sunday Reset and Daily Brief if they reference specific class names. Confirm the calendar connector is still pointing at this term's school calendar, not last term's.
Module 9 roadmap.
Module 9 in one card
- 9.1 (this one): what scheduled tasks are, what they aren't, the privacy posture, the audit habit, the plumbing test below.
- 9.2: Sunday Reset. Reads your calendar from Lesson 8.1, runs the Sunday Reset prompt from 8.2 inside your Coach Project from 7.2. Three optional variants ride along: Daily Brief, Friday Wind-Down, App Deadline Tracker. Pick zero, one, or all three.
- 9.3:Pre-Exam Watch. Tag your exams in the calendar; four nudges fire at the right intervals: T-5 days, T-3, T-1, morning-of. Each one runs real study work, not pep talks.
Try this: your first scheduled task is a plumbing check.
Before we wire up anything that matters, fire one throwaway task to confirm scheduled tasks are actually working in your account. This saves you debugging later when Sunday Reset doesn't fire and you can't tell whether the prompt is wrong or the plumbing is broken.
How to wire it up
In Claude, open the menu and find Scheduled Tasks (the exact menu name and location may shift as Claude's interface evolves: verify in your settings). Create a new task. Use any short prompt (e.g. "say hi"). Set it to fire 10 minutes from now, one time only. Save. Close the laptop. Set a phone timer.
10 minutes later, open Claude and check for a new chat with the message in it. If you see it: scheduled tasks are working. Delete the test task; it's done its job. If you don't see it: re-check Pro is active, re-check the schedule was set correctly, re-check the task wasn't saved as a draft instead of armed.
Up next: 9.2: Sunday Reset
The flagship scheduled task. We'll wire it up inside your Coach Project, calibrate it to your actual life (energy, sports, shifts, app season).
Continue to 9.2:Sunday Reset →