Reporting
What goes in an n8n monthly client report
A good client report does three jobs: tells the client their stack is healthy, names what changed, and quietly defends your retainer. Here is what to put in it, in what order, and what to leave out.
Why automation consultants need client reports at all
A retainer is a strange product. You charge a flat monthly fee, and the better you are at the work, the more invisible it becomes. A quiet month with no broken workflows is the BEST month — and it is the month the client most often questions the invoice.
The fix is an artifact. Once a month, you hand the client a PDF that summarizes their automation stack's health and what you did about it. It does not need to be long. It needs to be specific and consistent. The pattern below comes from watching ~15 consultants send (or fail to send) these reports.
The five sections that earn the retainer
1. Executive summary (3 sentences)
One paragraph addressed to the client by name. Lead with the headline number: total executions this month, success rate, anything critical that changed. Skip the boilerplate. The CFO scans this and decides whether to read further.
Example: “Your automation stack ran 3,412 executions in May at a 99.2% success rate. We caught two failures before they affected downstream systems and rebuilt the BigMarker → ClickUp sync after a BigMarker API change. No client-facing impact this month.”
2. Health distribution
A simple stacked bar showing how many workflows are healthy, warning, critical, stale, and unknown. Health is a category, not a number — a score of 67 means nothing to a client. “3 critical, 5 stale, 42 healthy” means everything.
3. Needs attention
A short table of workflows that scored below threshold this month and what's wrong with each. Keep it to the worst 10. For each, name the workflow, name the primary issue (high error rate, not running recently, no owner assigned, etc.), and where appropriate, a one-sentence action.
4. What changed
This is the part that proves you're working. New workflows added. Workflows you retired. Owners assigned. Credentials rotated. Two or three bullets is plenty. If nothing changed, say so — that's a good month, not an empty section.
5. Full inventory
A condensed table of every workflow with its status, score, trigger type, connected apps, last run, and error count. The client probably won't read it. That's fine. Its presence signals that you're tracking everything, and three months in, when the client asks “wait, what does Process leads from Salesforce actually do?” you can point at the row.
What to leave OUT
- Marketing language.No “unlock”, no “supercharge”, no exclamation points. The client is paying for operations, not for a sales deck.
- Vanity metrics. Total executions across all time. Bytes processed. The number of nodes. Skip them. Stick to numbers that change something.
- n8n branding.The report should be in your agency's brand, not n8n's and not your monitoring tool's. The client doesn't care what stack you use; they care what you did.
- Technical jargon by default.“Webhook timeout” is okay because clients have heard of webhooks. “NodeOperationError in the executeAdditionalFields method” is not okay because the only reader who'd understand it is you.
The white-label question
The report needs to look like it came from your agency. If your tool puts its own logo on the PDF, you become an intermediary instead of the trusted operator. The right pattern: your logo, your primary color accent, your contact email in the footer.
That's why WorkflowRadar's reports never carry our branding. We're the rails; you're the brand.
Generating reports without doing the writing
The blocker for most consultants is the writing. An AI-generated executive summary, drafted from the actual workflow counts and recent issues, gets you 80% of the way. You edit the last 20% to add context the AI can't see — what the client asked for, what you fixed.
WorkflowRadar does exactly this: it builds the report from your workspace's data, drops in an AI-written summary, and gives you a notes field for the human paragraph. Total time per client per month: under five minutes.
Cadence and delivery
Monthly is the sweet spot. Quarterly is too infrequent — clients forget you're working. Weekly is too noisy — clients stop reading. Send on the first Tuesday of the month with a one-line message in the email. Don't embed the PDF in a long email; attach it and let the file do the work.
The report generator ships in every paid tier. Sign up free below and upgrade when you want it.