Automate Monthly Reporting Pack Assembly

Workflow area: Automation · Tier: Advanced · Hands-on time: ~45 minutes to design; a half-day to build

The right target for automation is the assembly, not the judgment. Numbers still come from their owners; the commentary still gets a human edit. What disappears is the copy-paste choreography in the middle — the part nobody's judgment was improving anyway.

When to use — and when not to

• Use it for genuinely recurring packssame sections, same sources, every month. The build cost pays back from month two.
• Use it where inputs are already structurednumbers land in Sheets, exports arrive as CSV, section owners can fill a form. Structured in, assembled out.
• Skip it if the pack's structure changes monthlyyou will spend more time re-wiring the flow than writing the report. Stabilize the template first, then automate.
• Skip the auto-send, permanentlythe pack goes to a reviewer, never straight to leadership. An AI-drafted commentary error in a circulated management report is a career-grade incident.

The recipe

1. 1.

   Map the pack before touching n8n. List every section of the current report: its data source (sheet, export, owner), its commentary author, and its format. Classify each section: data-only (table, no prose), data + commentary (the AI-draft targets), or judgment (outlook, risks — human-written, automation just reserves the slot). This map is the workflow design.

2. 2.

   Standardize the inputs. Create one Google Sheet as the collection point — a tab per section, fixed column layout, and a status row the section owner flips to "ready". Where owners currently email numbers, give them a form that writes to the tab instead. The automation's reliability is decided here: flows fail on input chaos far more than on node logic.

3. 3.

   Build the n8n skeleton. Nodes in order:

   • •
     Schedule Trigger — e.g. 3rd working day, 09:00.
   • •
     Google Sheets nodes — read each section tab.
   • •
     IF node — check every status row says "ready"; if not, branch to a Slack/email nudge to the missing owners and stop. Do not draft commentary on incomplete data.
   • •
     AI node per commentary section (Claude via the Anthropic node or HTTP Request) — one call per section, not one giant call.
   • •
     Google Docs node — create the pack from a template, insert tables and drafted commentary into placeholders.
   • •
     Email/Slack node — notify the human reviewer that the draft is ready, with the doc link.
4. 4.

   Write the commentary prompt per section — this is where quality lives.

   Copy

   You draft commentary for the "[SECTION NAME]" section of a monthly
   management report.
   
   This month's data:
   [TABLE FROM SHEET — inserted by n8n expression]
   Last month's data:
   [PRIOR TABLE]
   
   Write exactly 3 short paragraphs:
   1. What changed vs last month — cite only numbers present in the
      tables above, with direction and magnitude.
   2. Why it matters for the business.
   3. What to watch next month.
   
   Rules: perform no arithmetic beyond reading values from the
   tables. If a comparison requires a number not present, write
   [DATA MISSING: description] instead of estimating. Neutral
   management-report tone. British/Indian business English.
   Never invent causes — if the driver of a change is not evident
   from the data, say "driver to be confirmed by [SECTION OWNER]".
   

   The "no arithmetic" and "never invent causes" rules are the difference between commentary a reviewer lightly edits and commentary they must forensically re-check.

5. 5.

   Add the reliability layer. Three additions before this runs unattended: an error workflow (n8n's error trigger) that alerts you when any node fails; idempotency — the flow writes a "run completed for [month]" marker and refuses to double-run; and a kill switch — deactivating the workflow must be a one-click act every stakeholder knows about. Name an owner for the flow; automations without owners rot into silent failure.

6. 6.

   Run one month in shadow mode. Let the automation produce its pack while you still build the manual one. Diff them: every number in the automated pack must match, every commentary paragraph gets graded. Fix the prompt or the mapping, not the output. Only after a clean shadow month does the automated pack become the primary draft — still human-reviewed, forever.

Make it yours

• Power Automate / Zapier version. M365 shops: Scheduled cloud flow → Excel Online tables → AI step per section → populate a Word template → Teams approval to the reviewer. Zapier: Schedule → Sheets reads → AI steps → Google Docs template → Gmail draft. The architecture — gate on readiness, draft per section, human review — is identical.
• Reviewer checklist in the notification. Have the final node include a three-line checklist in the reviewer email: "Verify all [DATA MISSING] flags resolved. Spot-check 3 numbers against source tabs. Read commentary for invented causes." Cheap insurance, every month.
• Section-owner sign-off variant. For high-stakes packs, insert an approval step per commentary section routed to its owner before compilation — slower, but every paragraph gets domain-expert eyes.

Quality check

• The flow refuses to run on incomplete inputsmissing sections trigger nudges, not guesses.
• Commentary prompts forbid arithmetic and invented causesflags instead of fabrications.
• A human reviewer stands between the flow and every recipientno auto-distribution path exists.
• Error alerts, idempotency and a kill switch are wired inand the flow has a named owner.
• One shadow month passed with numbers matching the manual packbefore the automation became primary.