Automate your Monday numbers: a weekly business report with Grok Bot (unofficial guide)

The short answer

Pick the five to seven numbers you actually make decisions on, show the Bot where each one lives, and ask for last week compared with the week before, with anything that moved more than a set percentage flagged.

Run it by hand until the report is right, save the instructions as a skill, then ask the Bot to run it every Monday morning as a routine. Have it return a draft for you, not send it to the team on its own.

This guide is independent and unofficial. It isn't affiliated with or endorsed by xAI, Grok, X, or Cursor. Features change often, so check the linked docs.

Step 1: decide the numbers and where they live

Write the list first: for example revenue, orders, ad spend, leads, cash in the bank, and anything low in stock. A short list you trust beats a long one nobody reads.

For each number, name the one source of truth: a spreadsheet, a dashboard, a report email, or an app. The official docs say memory isn't a source of truth, so the Bot should reopen the source every week instead of remembering last week's figure.

Use a connected app where one exists. Open Connect apps from the sidebar, add the app, and finish the sign-in. Per the docs, apps are more reliable than clicking through a website, and the Bot can read and edit cells in Google Sheets the connected Google account can edit.

If a tool has no app, two fallbacks work: have the tool email you a scheduled report and let the Bot read it from your connected inbox, or let the Bot open the site in its browser using a login you've saved in Vault.

Step 2: build the report once, then save it as a skill

Ask in chat: pull each number for last week and the week before, show the change, and flag anything that moved more than your threshold (20% is a reasonable start). Ask for a five-line summary on top and the table underneath.

Check every figure against the source the first time. When something's off, correct it in plain words ("revenue should be net of refunds") until the report matches what you'd have written.

Write down the exceptions before you automate. Every business has them: a refund that lands a week late, a holiday week, an ad account billed monthly. Put them in the instructions so the Bot doesn't flag the same false alarm every Monday.

Then say "Save this as a skill called Weekly numbers." A skill is the recipe for how to do the task; our guide to teaching a Bot a task covers the details.

Step 3: put it on a Monday routine

Ask the Bot that owns the job: "Every Monday at 7:00 AM, run my Weekly numbers skill and send me the draft." A routine is the timer that tells one Bot when to run a workflow, and it runs in the cloud while your laptop is closed.

Schedules follow the time zone set under Settings → Bot, and a new routine waits for its next scheduled time. Use Test to try it right away; a test does real work, so it uses usage too.

Keep the report a draft. The docs' advice for routines is to automate preparation before execution and keep sending behind approval. Have the Bot draft the team message in Slack or email and wait for your OK.

One weekly run is cheap. If your weekly usage runs low, the docs suggest widening schedules before raising a plan or limit.

Keep the numbers honest

Add a no-data and stale-data rule, which the official docs recommend for every routine: if a source is missing or hasn't updated since last week, the report says so instead of reusing an old number or estimating one.

Ask for a link or file name next to each number so you can check it in one click.

Ask for totals that tie back to the source. The docs' expense manager example asks for totals that reconcile back to the source, and the same habit catches mistakes in a sales report.

Re-test the skill whenever a spreadsheet's columns or a report's format change. The docs list that as a routine-design rule too.