Weekly Digest Email

The Value of Automated Digests

Weekly digest emails are one of the highest-value low-complexity automations available. They surface data that otherwise lives in silos — spread across spreadsheets, dashboards, and apps that team members rarely check. Done well, a weekly digest replaces a manual reporting task that takes 30–60 minutes and turns it into a workflow that runs while you sleep.

Defining What Goes in the Digest

Before building, list every metric or update that belongs in the digest. A typical business digest might include: revenue this week (Stripe), new leads (HubSpot or Sheets), content published (Airtable), open support tickets (Zendesk or Notion), and a brief AI-generated commentary on the week's highlights. Each data source becomes one section of the email.

The Workflow Architecture

1. Schedule Trigger — set to run every Monday at 8:00 AM.
2. Parallel data fetching — use multiple nodes in parallel to pull data from each source simultaneously:
   • Google Sheets node → weekly revenue rows
   • HubSpot or Airtable node → new leads count
   • HTTP Request → any other data source with an API
3. Aggregate nodes — calculate totals and week-over-week changes for each metric.
4. Code node — assemble all the aggregated data into a single object, ready for the email template.
5. Basic LLM Chain (optional) — pass the week's numbers to an LLM and ask for a 2–3 sentence executive summary of the key highlights and any anomalies. This adds a layer of insight the raw numbers alone do not provide.
6. HTML email template — build the email body in the Code node using inline-styled HTML: a header with the date range, metric cards for each data source, the AI summary paragraph, and a footer with unsubscribe link.
7. Gmail or SendGrid node — send to a list of recipients stored in an Airtable or Sheets subscriber table.

Week-over-Week Comparisons

To include percentage changes, your Google Sheets revenue log needs to store data by date. Add a filter in the Sheets query to fetch last week's totals separately, then calculate the change in the Code node: (thisWeek - lastWeek) / lastWeek * 100. Format the result as a coloured arrow (up in green, down in red) in the HTML template — this makes the digest immediately scannable.

Testing Before Enabling

While building, set the Schedule Trigger to test mode and run it manually. Before enabling the live schedule, run the workflow once with the Gmail node configured to send only to yourself. Verify all data sources are returning the right data, the formatting looks correct, and links work. Switch to the full recipient list only after this confirmation step.