Automate a recurring Excel report with GPTExcel workflows: build it once, run it every week
A weekly sales report you rebuild by hand every Monday, turned into a GPTExcel workflow. Save it from the chat, run it on next week's file, put it on a schedule, and check each run in its history.
Most spreadsheet work isn't new. Every Monday someone exports last week's sales, removes the test orders, totals revenue by region, compares it with the week before, adds a chart and sends the summary round. The steps are the same each week and only the file changes. That kind of task is what GPTExcel's workflows are for: you do it once in a chat, save it, and from then on it runs from a single click or on a schedule.
This post walks through it with a weekly sales report.
The starting point
The weekly export is a CSV with one row per order: the order date, order ID, region, product, quantity, revenue and a status column. A few rows each week are test orders or cancellations that shouldn't count.
The report the team wants has three parts:
- Revenue and orders by region for the week, compared with the previous week.
- A chart of revenue by region.
- A short written summary: what went up, what went down, anything unusual.
1. Do it once in a chat
Attach this week's export to a new chat and describe the report the way you'd explain it to a colleague:
Remove test orders and cancelled orders. Then give me revenue and order count by region for this week, compared with last week, with the change in percent. Chart revenue by region and write a three-sentence summary of what changed.
GPTExcel reads the file, cleans it, builds the table and the chart, and writes the summary. Look at the result the way you'd check a colleague's work. If something is off, say so in the same chat:
Count "Refunded" as cancelled too, and sort the regions by revenue.
Keep going until the report is the one you want. The chat now holds a worked example of the whole task, which is what the workflow is built from.
2. Save it as a workflow
In the same chat, ask:
Save this as a workflow I can run every week
GPTExcel turns what it did into a list of steps (clean the export, total by region, compare with last week, chart, summarize) and shows a workflow card with Run, Edit and Schedule. It saves the input it needs, the weekly export, as a file you attach each run.
Open Edit to check the steps. Each one has a plain-English instruction you can change, and Enhance rewrites a step more clearly if it reads vaguely. A few things worth setting while you're there:
- Saves as: a file name for a step's output, such as
Weekly-sales-report.xlsx, so the file is easy to find in each run. - Files kept with the workflow: if the report always uses the same template or a lookup table (sales targets by region, say), keep it with the workflow so every run has it without you attaching it.
- Model: the tier every run uses. A routine report like this one usually runs well on Fast.
3. Run it on next week's file
Next Monday, open Workflows in the sidebar and click Run. A new chat opens with the workflow in the message box. Attach the new export and send. You don't need to type the instructions again. If this week is different, add a line, such as "also flag any region that dropped more than 10%", and the run takes it into account.
Each run is a normal chat. You can ask follow-up questions about the numbers in it, download the files it made, or save the result to Google Drive or OneDrive.
4. Put it on a schedule
A workflow can run unattended only if it doesn't need you to attach anything. Here that means taking the weekly export from somewhere GPTExcel can reach on its own. On a Team plan, the input can be set to the newest file in a team folder, so whoever exports the sales drops the file in the team's folder and the workflow picks it up.
Once the workflow runs on its own, click Schedule and choose Every week, the day, the time and your time zone. Every Monday at that time it runs in a new chat, and the chat shows a dot in the sidebar until you open it.
If a run fails or can't start, for example because there are no credits left, you get a notification. After 3 in a row the schedule pauses itself so it doesn't keep failing quietly, and you can Resume it after fixing the cause.
Schedules depend on the plan: Plus has 3 active schedules, and Pro, Team and Business have no limit. The pricing page has the details.
5. Check the run history
The history button next to the workflow lists every run, whether it was started from a chat, in the background or by the schedule. Details shows each step with any errors, the files the run started with and the files it produced, and the credits it used.
If a run stopped for a reason that has since gone away, such as running out of credits, use Re-run with the same inputs. It runs again in the background, in a new chat, with the same files, and the failed run stays in the history for comparison. If the file itself was the problem (a column renamed in the export, say), click Run and attach a corrected file instead.
Tips for workflows that keep working
- Do it in a chat first. A workflow saved from a finished chat starts from a worked example, so its steps are usually closer to what you want than ones written from scratch.
- Name columns in the instructions. "Total the Revenue column by Region" survives a reordered export better than "total column F".
- Say what to do with bad rows. Test orders, blanks and duplicates are where reports drift from week to week. Put the rule in a step.
- Run it by hand once before scheduling it, on a real file, and read the result.
- Change it from the chat. In a chat where the workflow ran, "change the workflow to also include returns" updates the saved workflow rather than making a copy.
The full reference, including inputs, team sharing and limits, is in the workflows guide.