Key Takeaways
- A recurring task is a standing instruction plus a schedule. You describe the job once, say when it should run, and your AI employee handles it from then on.
- The best first recurring task is a report you already re-request by hand, like a Monday pipeline summary or a Friday numbers roundup.
- Say when, where, and in what shape. "Every Monday 8am, post it in
#revenue, as five bullets" turns a vague ask into a reliable routine. - Keep a checkpoint on anything that leaves the building. Have it draft and show you first until you trust the output, then let it send on its own.
- Point it at the right account and channel. A recurring task only works if the tools it needs are connected and it lives in the channel where the result belongs.
- Review the routine every few weeks. Standing tasks should be pruned and adjusted, not set once and forgotten.
The report you keep asking for by hand
Think about the thing you ask for every week. The Monday pipeline summary. The Friday roundup of last week's numbers. The month-start recap of new signups. You know exactly what you want, you know where it lives, and you type more or less the same request every single time. That repetition is the clearest signal you have that a task is ready to become recurring.
The Slack 2024 Workforce Index found that desk workers spend around a third of their day on low-value work, and re-requesting the same report is a textbook example. A recurring task takes that whole loop off your plate: you set it up once, and your AI employee runs it on the schedule you choose, delivering the result where you need it. Here is how to set one up so it is reliable from day one.
What a recurring task actually is
Answer first: a recurring task is a standing instruction paired with a schedule, so your AI employee runs the same job automatically at the times you set.
There is no complicated setup to learn. You are doing two things at once: describing the job the way you would describe any task, and adding when it should repeat. The AI employee remembers both, and from then on it does the work without you having to ask again.
That means a good recurring task starts as a good one-time task. If you can hand a job over clearly for a single run, you can turn it into a routine. Our guide on How to Write Tasks for Your AI Employee covers how to phrase the job itself. This post is about the part that makes it repeat.
Start with a report you already re-request
Answer first: the best first recurring task is something you already ask for on a regular rhythm, because you know exactly what good looks like.
Do not start with something new and ambitious. Start with a job you already do by hand every week, because you can judge instantly whether the automated version is right. Good candidates look like this:
- A Monday pipeline summary pulled from HubSpot and posted to your team channel.
- A Friday numbers roundup from Stripe, framed as the three figures that moved most.
- A weekly open-issues digest from Linear so nothing important goes stale.
- A start-of-month recap of new documents added to a Google Drive folder.
Each of these is something you can look at and immediately know whether it nailed it. That is exactly what you want for your first recurring task, because it lets you build trust quickly before you hand over anything more consequential.
Say when, where, and in what shape
Answer first: a recurring task becomes reliable when you specify the schedule, the destination, and the format, not just the job.
The difference between a routine that works and one that drifts is precision on three things: when it runs, where the result goes, and what shape it takes. Put all three in the instruction:
@Viktor every Monday at 8am, pull last week's closed deals from HubSpot and post a summary in #revenue: total closed, top three deals by size, and anything stuck in "negotiation" over 30 days. Keep it to five bullets.That single instruction sets up a task that will run reliably, because there is nothing left to guess. The timing is fixed, the destination is named, and the shape is defined. Compare that to "send me a weekly deal update," which leaves the AI employee to guess when, where, and how much, and gives you a slightly different thing every week.
You can set up more than one, each with its own rhythm and channel:
@Viktor on the first of every month, list every new file added to the "Board Reports" Google Drive folder last month and post the list in #board-prep as a simple bulleted index with links.Notice each recurring task does one clear job and lands in one clear place. That is what keeps a set of routines manageable rather than noisy.
Keep a checkpoint until you trust it
Answer first: for any recurring task whose output leaves your team, have it draft and show you first, then let it send on its own once the output is consistently right.
This is the single most important habit for standing tasks, because a recurring task by definition runs when you are not watching. You want to earn trust before you step back. The pattern is simple: for the first few runs, have it prepare the result and show it to you rather than sending anywhere external.
@Viktor for the first month, run the Monday summary but post it to me in a DM first so I can check it before it goes to #revenue. Once I say it's solid, switch to posting it in the channel directly.This mirrors long-standing guidance on running agents safely. Anthropic's engineering write-up on building effective agents makes the point that agents are most dependable when they operate inside clear boundaries with a human reviewing consequential steps. A recurring task that posts internally is low-stakes; one that emails customers or updates records is not, and those deserve a checkpoint until the pattern is proven. Start supervised, then graduate to autonomous once you have seen it get the job right several times in a row.
Make sure it can actually reach the work
Answer first: a recurring task only runs if the tools it needs are connected and the AI employee is in the channel where the result belongs.
Two practical things trip up otherwise well-written routines. First, the task needs live access to its source. If your Monday summary reads from HubSpot, the HubSpot connection has to be in place and not expired, or the routine will stall. If you are unsure, our guide on Why Your AI Employee Can't Access a Tool walks through the usual causes.
Second, the AI employee has to be a member of the channel where the result should land. A task that posts to #revenue needs the AI employee present in #revenue. And if the source tool has more than one account connected, name the one it should read, so the routine always pulls from the right place. Get these plumbing details right once and the schedule takes care of the rest.
Prune your routines every few weeks
Answer first: recurring tasks should be reviewed and adjusted regularly, not set once and left to run forever.
The failure mode with standing tasks is not that they break, it is that they quietly outlive their usefulness. A report you needed during a launch may be noise a month later. So every few weeks, glance at what is running and ask three questions: is anyone still reading this, is the shape still right, and is the timing still useful? Then adjust.
You can even ask the AI employee to help you audit:
@Viktor list every recurring task you're currently running for me, with the schedule and where each one posts, so I can decide what to keep.Keeping a short, deliberate set of routines beats accumulating a pile of standing reports nobody reads. A recurring task is a commitment of attention, both yours and the AI employee's, so spend it where it still earns its place.
Frequently Asked Questions
What makes a good first recurring task?
Something you already request on a regular rhythm, like a weekly pipeline summary or a Friday numbers roundup. Because you know exactly what a good version looks like, you can judge the automated result instantly and build trust fast.
How do I set the schedule?
Say it in plain language as part of the task: "every Monday at 8am," "on the first of the month," "every Friday afternoon." Pair the timing with where the result should go and what shape it should take, and the routine runs itself from there.
Will it send things without me seeing them first?
Only if you let it. For anything that leaves your team, have it draft and show you the result for the first several runs. Once the output is consistently right, you can let it post or send on its own.
What happens if the tool it needs stops working?
The routine will stall rather than send something wrong. Usually the fix is reconnecting an expired tool or making sure the AI employee is in the right channel. Keeping connections healthy is what keeps recurring tasks dependable.
Can I run more than one recurring task?
Yes. Set up as many as you need, each with its own schedule, destination, and format. Keep each one focused on a single clear job so the set stays manageable rather than noisy.
How do I stop or change one?
Just tell it. Ask it to list what it is running, then say which to pause, adjust, or reschedule. Reviewing your routines every few weeks keeps the useful ones and clears out the rest.
How is this different from a one-time task?
A one-time task runs once when you ask. A recurring task is the same kind of instruction with a schedule attached, so it repeats automatically until you change or stop it.
Set it up once, get it back every week
The tasks worth automating first are the ones you already do by hand on a schedule. Describe the job clearly, say when and where it should run and in what shape, keep a checkpoint until you trust the output, and make sure the AI employee can reach its tools and channels. Then review the set every few weeks so it stays useful. Do that, and the report you used to re-request every Monday simply shows up, done, without you asking.
Add Viktor to your workspace and set up your first recurring task
Related reading: