Reporting Ops

Weekly Operations Summary Sent to the Owner

A scheduled job pulls the week's key numbers from across tools, assembles one plain-language summary, and delivers it to the owner every Monday so the weekly review stops being a manual data pull.

Start a ProjectAll Case Studies
3 to 6 days
build time
4
outcomes
5
stack tools
6
build steps

Built with real HMX tool paths

nn8n (cron)
GGoHighLevel API
SStripe API
RResend
SSlack
nn8n (cron)
GGoHighLevel API
SStripe API
RResend
SSlack

Outcome signals

These are the real outcome statements attached to this HMX case study.

Automatic
weekly summary lands without a manual data pull
Deltas
week-over-week changes surfaced, not just raw totals
Consistent
same report every week, never skipped
Degrades
a dead source is flagged, the report still ships

Case architecture

Weekly Operations Summary Sent to Architecture

6 nodes
Schedule the workflow to run
Query each source for the
n8n
GoHighLevel API
Exception Path
Completed Workflow
  1. 01Schedule the workflow to run

    A scheduled job pulls the week's key numbers from across tools, assembles one plain-language summary, and delivers it to the owner every Monday so...

  2. 02Query each source for the

    Query each source for the week's counts, bookings, payments, and pipeline changes

  3. 03n8n

    n8n (cron) carries Weekly Operations Summary Sent to through validated triggers, branches, writebacks, and exception paths.

  4. 04GoHighLevel API

    Compute week-over-week deltas and flag notable movements

  5. 05Exception Path

    When automation confidence is low, route the record to a manual owner with the source, stage, and last action attached.

  6. 06Completed Workflow

    Automatic weekly summary lands without a manual data pull; Deltas week-over-week changes surfaced, not just raw totals; Consistent same report ever...

Problem

The operating gap

The owner's weekly review means logging into three or four tools, copying numbers into a doc, and eyeballing what changed. It's slow, easy to skip, and inconsistent week to week, so trends and exceptions get missed.

Build

What gets built

A scheduled workflow runs on a fixed cadence, queries each source for the week's counts and changes, computes deltas against the prior week, and formats a clean summary highlighting what moved and what needs attention. It delivers via email and a Slack post, with a link to the underlying records. If a data source is unreachable, the report still sends with that section clearly marked as unavailable rather than failing the whole run.

Build steps

Weekly Operations Summary Sent to the Owner uses an event-driven automation layer for AI Automation. A scheduled job pulls the week's key numbers from across tools, assembles one plain-language summary, and delivers it to the owner every Monday so... The architecture connects schedule the workflow to run, n8n, gohighlevel api, and completed workflow with an explicit control path.

  1. 01Schedule the workflow to run weekly at a fixed time and timezone
  2. 02Query each source for the week's counts, bookings, payments, and pipeline changes
  3. 03Compute week-over-week deltas and flag notable movements
  4. 04Format a plain-language summary with an 'attention needed' section
  5. 05Deliver via email and Slack with deep links to the records
  6. 06Mark any unreachable source as unavailable so the report still sends

Stack

Tools and layers

  • n8n (cron)
  • GoHighLevel API
  • Stripe API
  • Resend
  • Slack
  • Event layer: Schedule the workflow to run weekly at a fixed time and timezone
  • Validation layer: Query each source for the week's counts, bookings, payments, and pipeline changes
  • Branching layer: n8n (cron) carries Weekly Operations Summary Sent to through validated triggers, branches, writebacks, and exception paths.
  • Writeback layer: GoHighLevel API handles routine steps while a scheduled workflow runs on a fixed cadence, queries each source for the week's counts and changes, computes deltas against the prior week, and fo...
  • Exception layer: Automatic weekly summary lands without a manual data pull; Deltas week-over-week changes surfaced, not just raw totals; Consistent same report ever...

Data flow

  1. 01Schedule the workflow to run weekly at a fixed time and timezone
  2. 02Query each source for the week's counts, bookings, payments, and pipeline changes
  3. 03Compute week-over-week deltas and flag notable movements
  4. 04Format a plain-language summary with an 'attention needed' section
  5. 05Deliver via email and Slack with deep links to the records
  6. 06Mark any unreachable source as unavailable so the report still sends

Controls

  • The owner's weekly review means logging into three or four tools, copying numbers into a doc, and eyeballing what changed.
  • A scheduled workflow runs on a fixed cadence, queries each source for the week's counts and changes, computes deltas against the prior week, and fo...
  • When automation confidence is low, route the record to a manual owner with the source, stage, and last action attached.

Research basis