Claude can now run your Shopify store checks while you sleep

Claude can now run operations without you being there.

The feature is called scheduled tasks.

You write a prompt once and pick how often it should run. It shipped a few weeks ago and I've been testing a few on live stores.

The point isn't the few minutes it saves. The checks worth automating are the ones you'd never think to run in an ordinary week. So the test I use before scheduling anything is whether the answer changes while I'm not looking. If it does, it's a candidate.

How it works

A scheduled task is like a saved prompt with a clock on it.

You pick the cadence when you set it up, from hourly to daily to weekly to weekdays only. Each run opens a fresh session and reads your connectors at that moment, so a task pointed at Shopify and Klaviyo pulls live data every time it starts.

The part that makes it usable is that these runs happen remotely. A Cowork schedule keeps its cadence even when your laptop is asleep or closed, because the run isn't sitting on your machine. You set it up with the /schedule command inside any task, or from the Scheduled tab in the sidebar, and you can choose which model handles it.

What I'd actually schedule for a store

Here are three examples and each maps to something an operator does by hand.

1/ A replenishment check that runs every Monday.

It reads each customer's reorder gap against how long it's genuinely been since they last ordered, and returns whoever has crossed their personal due date.

A store-wide "email everyone quiet for 30 days" misses most of them, because a coffee subscriber and a mattress buyer don't run on the same clock.

2/ A churn tracker, every Tuesday.

It pulls repeat buyers who are past their expected next order and ranks them by how much they're worth against how likely they are to be gone. That list lands before I build the week's sends, while there's still time to do something with it.

3/ An AI visibility check, running once every week.

This is the clearest case of an answer that changes while you're not looking. An app update can alter your schema. A theme change can strip JSON-LD out of pages. Check it once a quarter and you will end up finding out too late.

A weekly pass catches the slip close to when it happens.

How to set one up

The setup flow is short, and easier to show than describe.

Open a fresh Cowork task and type /schedule, followed by the cadence and the prompt you want it to run. For the churn tracker I just described, looks roughly like this:

/schedule every Tuesday at 9am, run the churn-risk ranked list from The Agentic Operator. Repeat buyers with at least two orders and a churn probability of 0.6 or higher whose next order date has passed. Rank by predicted CLV times churn probability. Read-only.

Claude reads the whole thing back to you before saving it, including the connectors it'll pull from. If something is off, you fix it in the same conversation and confirm. The task lands in the Scheduled tab in the sidebar, ready to fire on schedule from then on.

The manual version of the same thing sits under "New task" on that same Scheduled page, if you'd rather fill in the fields directly. Either way, it’s the same schedule.

A few things break the first time you set one up - worth checking before you trust a schedule to run alone. Also name the exact task, not the topic.

A vague prompt gets a clarifying question back, and at 9 am there's nobody there to answer it, so the run just stalls. Tell it to read the shop name off the connection and stop if it doesn't match, since the schedule fires against whatever account is connected that morning. And put read-only in the prompt in plain words. The default is read-only. But if a run decides it wants to write something, there's no one to approve it either way.

One place to run them from

All three examples are on the same skill I built, called The Agentic Operator.

There are 62 prompts across nine domains. Each returns its answer in a fixed shape. That fixed shape is what makes them worth scheduling. When the output looks the same every run, you can read a week's results at a glance and catch the run that came back wrong.

Download and add the skill, point a schedule at whichever prompts fit how you run your store, and set the cadence. Get the Claude skill here →

- Ankit