Set it up once, get the result every time
Recurring tasks are OperatorNest’s standing orders: work you’d otherwise repeat by hand on a schedule, handed off once and run automatically from then on. You describe what you want and how often, and your operator takes it from there, on time, every time, without you having to remember to start it.
This is different from a one-off task. A one-off runs once and finishes; a recurring task keeps running on the cadence you set until you change or stop it.
What a schedule looks like in practice
You can describe a recurring task the way you’d say it out loud. For example:
- “Every weekday at 8 a.m., summarize what came into my inbox overnight and flag anything that needs a reply.”
- “Every Monday, pull what our three main competitors changed on their pricing pages and their blogs, and send me a one-page brief.”
- “On the 1st of each month, check which invoices from last month are still unpaid and draft reminder emails.”
Your operator turns that into a schedule, runs it at the time you set, and delivers the result to the channel you asked from, whether that’s WhatsApp, Slack, email or the web.
What happens on each run
Every run follows the same shape. Your operator checks the sources relevant to that task, whether that’s an inbox, a set of competitor pages, a spreadsheet or a calendar. It compares what it finds to the last run, so a competitor brief highlights what actually changed rather than repeating the same facts every week. It prepares the output, whether that’s a summary, a set of drafts, or a status update. And if the run needs a decision from you, like sending the invoice reminders it drafted, that step waits for your approval the same as any other task; see approvals.
A run that finds nothing new says so plainly, rather than padding out a report. A recurring task you can’t trust to be honest about “nothing changed” isn’t one you’ll keep reading.
Where recurring tasks fit best
They work best for anything with a natural cadence and a clear question at the end of it: is there anything I need to see or do. Common patterns include a daily inbox digest, a weekly competitor or market brief, a monthly invoice follow-up, a weekly review of open follow-ups, or a recurring check on a price, a listing or a filing deadline. See competitor monitoring and invoice follow-up for two fully worked examples. For provider schedules and missed-run policies, read the scheduled AI task comparison.
A daily research digest can also take the form of an AI morning brief, with sources and open decisions ready at the start of the day.
They’re not the right tool for a single piece of research or a task with no repeat cadence; a background task covers that instead.
Recurring tasks and always-on work
Recurring tasks are one of the main reasons an always-on agent is useful rather than just available. A schedule doesn’t need you to remember it, open an app at the right time, or even be awake. Your operator checks the clock, not you, and a 7 a.m. brief is genuinely waiting at 7 a.m., not whenever you next think to ask for it.
This is also where recurring tasks differ from a single background task. A background task runs once, however long it takes, and finishes. A recurring task runs the same shape of work repeatedly, on a cadence, and its value builds across runs, not any one result alone.
Staying in control of the schedule
A recurring task is easy to change because it’s never hidden. You can see every task you’ve set up, when it last ran, and what it’s scheduled to do next. Editing the cadence, the sources it watches, or what it delivers takes effect from the next run. Pausing a task keeps its setup and history intact, so you can turn it back on later without rebuilding it. Deleting it removes it for good.
If a recurring task starts producing something you don’t want, such as reminders phrased too bluntly, you can correct it once and it carries that correction into future runs; see memory for how that works.
Every run is on the record
Each run of a recurring task is logged on its own: when it ran, what it checked, what it found, what it produced, and any decision you made along the way. If a weekly brief flagged something three weeks ago that turned out to matter, you can go back and see exactly what it said and when; see receipts. A recurring task earns trust the same way a person doing the same job would: by being consistent and by leaving a clear trail of what it did each time. For a multi-check night watch, see the overnight competitor monitoring example.