Skip to content
AISCREENCASTS
Back to library

Automate Email Triage with Scheduled Tasks

You built the email triage skill. Now stop running it. In this episode, Jason schedules it to run at 5:30 every morning so your sorted inbox is waiting before your first coffee.

Pro episode

SUBSCRIBE TO WATCH

This episode is in the Pro library. Subscribe to watch it. Cancel anytime.

Transcript preview

So far, you've gone in here and connected your inbox to Claude. You've even built a triage skill that checks your email and triages it. And right now, every day, you have to go in there and run that triage skill, like /email-triage, to get that feedback from your inbox and pull that information.Except by the end of this video, we're going to cut that last string. By 5:30 every morning, this task is going to run for you, so the result is waiting for you when you sit down and have coffee. You'll have to do nothing.So far, everything has been about you talking to Claude and it answering. A schedu…

Subscribe to read the full transcript →

You've already connected your inbox to Claude and built an email triage skill. The last manual step is running it yourself every morning. This episode cuts that string. Jason walks through setting up a scheduled task in Cowork two ways: conversationally with "Create with Claude," and manually with a one-line instruction (/email-triage, daily, 5 a.m., act without asking). He covers why this particular task is a safe first automation (repetitive, time-boxed, low risk, nothing sends), how to test it with "Run Now," and how to review every past run. The bigger idea: a scheduled task flips the relationship. Instead of you prompting Claude, Claude initiates and you react to a finished result. Once one task earns your trust, you stack more (calendar at 5:15, LinkedIn at 4, a combined briefing at 6) until dozens run every day. Jason runs 36+ on a single cloud instance. Ends with a pointer to the Notion track for getting results out of Claude entirely and reducing vendor lock-in.