Claude Academy
Loading

Put recurring work on a schedule

Lesson 810 min
In this lessonBy the end, you’ll be able to
  • Set up a routine in one message with day, time, and format
  • Shape a routine by replying to its first post
  • List, change, pause, or stop the routines in a channel

Some work should happen continuously, on a schedule you choose, without you having to ask each time. This may look like a weekly report built from your team's tools, or a daily check that posts only when something needs attention.

Claude can run recurring work as routines: tell it once what the work is and when to run it, and instead of waiting for a mention it runs on that schedule and posts the results in the channel.

Types of routines:

  • Weekly or daily reports: A status digest, a summary of decisions made, a list of what's blocked or waiting.
  • Continuous monitoring: Watch a channel or repository for specific changes. When Claude finds something, it posts an alert or summary here.
  • Regular checks: Review what's pending, flag anything overdue or at risk, surface patterns that matter.

Instead of needing to tag Claude for the same task every week, you set it up once and it runs without you. Claude can keep watch in the channels and tools no one on the team has time to check.

How to set one up

Write one message that says what Claude should read, what to look for, what to post, and when. A routine runs with the tools connected to the channel, so it can compare sources and post only what needs someone's attention:

@Claude every weekday at 9am, compare the onboarding tracker with what was said in this channel yesterday, and post only what needs attention: anything overdue, and anything the thread says has slipped that the tracker still shows on time. Name the owner, link the message, and suggest a next step. If nothing needs attention, post nothing.

On a quiet day this routine posts nothing, so a post from it always means there is something to look at.

When the first result arrives, reply in that thread with what you want different. Claude reads your feedback, learns from it, and applies it to every run that follows. Treat that first post as a draft: a little shaping early keeps the routine useful and worth reading rather than one more message the channel scrolls past.

Check or change what is scheduled

Routines belong to the channel. Each one posts there for everyone to see, and anyone in the channel can list or change them:

  • List: ask @Claude what routines do you have set up in this channel? or send @Claude !routines.
  • Change or pause: describe the change, such as "pause the Monday digest until I say I'm back."
  • Stop: name the routine, such as "stop the Friday status."

A routine keeps running even if the person who set it up leaves the channel or the organization, and anyone still in the channel can pause or stop it.

Practice

Loading

Try it

Put one small task on a schedule

In your workspace · 5 minutes

  1. Pick something small you ask for every week.
  2. Send it in one message: what to read, what to post, when (day and time), the format, and what to do when there is nothing to report.
  3. Ask @Claude what routines do you have set up in this channel? to confirm.
  4. When the first post lands, reply in its thread with one change.

Done when: the routine list shows what you meant, and the first post's thread has your change.

Before you move on

Key takeaway: work that recurs can run without anyone asking.

After practicing: You will have one routine listed in a channel, with its first post adjusted from the thread.