How to Use Claude Scheduled Tasks to Update a Client Report at the Same Link

Published

A clock and a row of calendar days beside a report card with faded earlier copies behind it, tied by a blue ribbon to one tag that stays in place.

You send the same report every week: ad spend, leads, what changed, and what you are doing next. Building it takes 40 minutes. Sending it means a new PDF in an email thread that nobody can find on Thursday.

A Claude scheduled task can rebuild the report on a schedule and update a page your client already has. You send the link once. Each Monday, the task reads the new numbers, writes the new version, and replaces the page behind the same URL. This guide shows how to set it up, what to check before you trust it, and when not to do it.

What Claude scheduled tasks can and can’t do

Claude has two scheduling features, and the names have changed over time:

WhereWhat it isPlansSchedule
Claude app (Cowork and the new Claude experience)A prompt that runs on a schedule and can use the connectors you set upPro, Max, Ultra, Team, EnterpriseHourly, daily, weekly, weekdays, or manual
Claude Code (on the web)Scheduled tasks, formerly called routines: a saved prompt that runs as a cloud sessionPro, Max, Team, EnterpriseHourly, nightly, weekly presets, or custom cron no more often than hourly

Sources: Anthropic’s Cowork scheduled tasks article and the Claude Code scheduled tasks docs, read on November 13, 2026.

Two details matter for a client report:

  • Where the data comes from. Anthropic says Cowork tasks run remotely, so they keep their schedule when your computer is asleep. A task that needs local files or apps only runs locally. If your numbers live in a spreadsheet on your laptop, the task depends on that laptop. A connected Google Sheet or Drive file avoids that.
  • Where the result goes. A scheduled task can write a report, but by default the result stays in Claude. To put it in front of a client who doesn’t use Claude, the task needs a connector that can publish a page.

For the second part, this guide uses the Litehost connector, which publishes a page and can later replace what is behind the same link. Any host that offers the same “update in place” behavior works with the same method.

The setup has three parts. Most broken report automations skip the third one.

  1. One link the client keeps. You publish the first version by hand, check it, and send the link once. Every later run updates that page. Nothing else gets sent.
  2. A prompt that does not change. The scheduled task gets the same instructions every week: where to read, what to show, and which page to update. You change the prompt deliberately, not inside a run.
  3. A rule for when not to update. If the data is missing, incomplete, or looks wrong, the task stops and tells you, and the client keeps seeing last week’s report. A stale report is better than a wrong one.

Worked example: a weekly ads report for a plumber

An illustrative case: you manage Google Ads for Rivera Plumbing. The owner, Luis, reads reports on his phone, doesn’t log into Google Ads, and wants one answer: how many people called and what each call cost.

We built this report and published it on Litehost as rivera-ads.litepage.site. First we published it with September’s numbers. Then we updated it with October through the connector (update_project_files), and the link stayed the same. The page is a single HTML file with an inline chart and a campaign filter. We checked it on an iPhone. All names and numbers in it are made up.

On November 13, 2026, we ran three more checks on the same page. A Claude scheduled task in the desktop app fired on time and called the Litehost connector. An update sent from Claude kept the link. A rollback in the dashboard brought back the previous version. One limit showed up in those checks: the connector can’t read a page’s current files back, so the task has to build the whole page from the data every time instead of editing last week’s page.

Step 1: Publish the first version by hand

In a normal Claude chat with the Litehost connector added, attach the first export and ask:

Build a one-page report for my client Luis (Rivera Plumbing). He reads it on his phone. Show what he spent, how many calls he got, cost per call, the campaign that brought the most calls, and three plain-language notes on what we change next. Then publish it with Litehost and name the project “Rivera Plumbing – weekly report”.

Open the link in a private window and on your phone. Fix anything now. This is the page Luis will bookmark.

Step 2: Put next week’s data where the task can read it

Decide where new numbers will appear each week. Your options include a Google Sheet your team or a tool fills in, a CSV export dropped in the same Drive folder, or a file on your computer. With a file on your computer, the task runs locally.

Keep every week in that source, not only the newest one. The task rebuilds the whole page from the data each time, so the history table comes from the sheet, not from last week’s page. Use the same columns every week. The task follows your prompt, and a renamed column is the most common reason for a wrong number.

Step 3: Create the scheduled task

In Claude, create a weekly task, for example Monday at 8:00, with a prompt like this:

Read last week’s rows (Monday to Sunday) from the sheet “Rivera – weekly ads”.

If there are no rows for last week, or calls or spend are empty, do not update anything. Tell me what is missing.

Otherwise, build the report from the sheet: this week’s spend, calls, and cost per call, the change from the previous week, and three short notes. Put all earlier weeks from the sheet in a small table at the bottom. Keep the same sections and order every week.

Update the existing Litehost project “Rivera Plumbing – weekly report”. Do not publish a new link. Reply with the link and the three numbers you used.

The last line matters. Asking for the numbers back gives you a 10-second check in the task’s history each week.

Step 4: Run it once yourself

Use the manual run before you trust the schedule. Compare the numbers in the task’s reply with the sheet, and open the client link to confirm it shows the new week. Then leave it on the schedule.

Step 5: Know how to undo a bad run

If a run ever publishes a wrong number, open the project in the Litehost dashboard and roll back to the previous version. Luis’s link then shows last week’s report again while you fix the prompt or the data.

What it costs on the Litehost side

The first publish works on any plan. Updating an existing page through the connector, which is what the weekly task does, needs a paid plan (Starter or above). Free links show a small Litehost badge and stay online as long as they are opened at least once every 90 days. See the Litehost plans for prices and limits.

When not to automate the report

  • The client needs live data. If they want to filter by any date or check numbers daily, a live dashboard such as Looker Studio fits better than a weekly page.
  • You review every report before the client sees it. The update is visible the moment the task runs. If someone must approve each version, have the task send the draft to you and update the client page yourself.
  • The report is confidential. A public link opens for anyone who has it. Use a password-protected page (paid plans) or the channel your client’s policy requires.
  • The data source changes shape often. If columns change every week, fix the source first. Automation multiplies a messy input.
  • It’s a one-off. For a single report, publish it once and skip the schedule.

Before you leave it running

The test is not whether the first run looks good. It is whether the fourth run, on a week with odd data, either updates correctly or stops and tells you. Check the task’s history after the first few Mondays.

If you don’t have a page for the report yet, upload the HTML report to Litehost to get the first link. For exporting reports built in Claude, see How to Share a Claude Artifact With a Client Who Doesn’t Use Claude.