A shop owner sits down at the end of the week and counts what was sold from invoices and chats. It takes time, sometimes goes wrong, and gets forgotten if a few weeks slip by. With n8n automation the same report can be built automatically every week. This article shows how, and where you should not rely on it.
What is wrong with a manual report?
Three things: it takes time, it differs a little each time (once with shipping, once without) and it is the first thing dropped when you get busy. A report built the same way every week makes weeks comparable.
| Number | Why it matters | Where it comes from |
|---|---|---|
| Total weekly sales | The size of the business at a glance | The sales sheet or CRM |
| Number of orders | Separates volume from order value | The orders sheet |
| Average order value | Shows how much a customer buys | Total sales divided by orders |
| New versus returning customers | Shows where growth comes from | A customer’s first-purchase date |
- Schedule
It runs every week at a fixed time (say, Saturday morning).
- Read the data
Last week’s sales are read from the sheet or CRM.
- Compute
Total sales, order count, average and new customers.
- Build the message
A short message comparing with the week before.
- Send
The message lands in your Telegram or the team group.
How do you build the weekly report step by step with n8n?
- Create a sales sheet where each row is an order: date, amount, customer ID and status. If you have a CRM, use that; see a simple CRM for an online store.
- In n8n, build a workflow and set the Schedule Trigger node to a fixed time each week; n8n’s documentation explains this node.
- Read last week’s data from the sheet and use a calculation node to produce the four numbers above.
- Compare them with the previous week and build a short message: “this week’s sales X; compared with last week Y”.
- Send the message with a Telegram bot. The bot posts to your chat or the team group using the sendMessage method of the Bot API.
- Run the automatic report next to the manual one for two weeks and compare the numbers; trust it only when they match.
Where does AI fit in this report?
Do not leave the arithmetic to AI; code computes sums and averages more exactly. AI is useful only for writing a two- or three-line summary on top of ready numbers (“sales are up on last week, mostly from returning customers”). A good way is to read that summary yourself for a few weeks first and automate it only once it proves accurate. For the wider idea, read about intelligent automation.
What errors make an automatic report untrustworthy?
- Incomplete data: if sales are entered late, the report looks low. Set a fixed rule for recording orders.
- A vague definition: “sales” with or without shipping? With or without discounts? Define it once and keep it.
- Time and time zone: the week boundary differs from the server clock. Set the run time and week boundary explicitly.
- A silent failure: if the workflow breaks and no message arrives, you may think sales were zero. Also set up an error message.
Where should you not rely on an automatic report?
- Financial decisions and official accounting: the report is a quick view, not a ledger.
- A business with a few orders a week: one look at the sheet is enough and no automation is needed.
- A number with no clear source: tidy the data first, then automate.
- The reason behind sales: the report says how much you sold, not why. Analysing the cause is yours.
What is the first step?
- This week, work out the four numbers above by hand and note them.
- Tidy the sales sheet and fix the definitions.
- Keep the manual report for a month so you have a reference.
- Then automate the same thing in n8n and compare it with the manual one.
Frequently asked questions
How do you build an automatic weekly sales report?
Build a tidy sales sheet, then set up an n8n workflow with a weekly schedule that reads the data, computes a few key numbers and sends them through a Telegram bot. Compare it with the manual report for two weeks.
Do I need AI for a weekly report?
No. Code computes sums and averages more exactly. AI is useful only for writing a short summary on ready numbers, and it is best checked by your own reading first.
Why does an automatic report sometimes show a wrong number?
Usually because of incomplete data, a vague definition of “sales”, or the time and week boundary. Fix the definitions and set up an error message for workflow failures.
Does an automatic report replace an accountant?
No. The report is a quick view of sales; the ledger and official financial decisions stay with the accountant and you.