Block 1 - Every Monday at 08:00
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.2
Stop compiling your weekly business report by hand. Let automation pull the numbers, and let Claude write the narrative. Every Monday morning, this workflow fetches last week's revenue from Stripe,...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.code, n8n-nodes-base.googlesheets, @n8n/n8n-nodes-langchain.chainllm, @n8n/n8n-nodes-langchain.lmchatanthropic, n8n-nodes-base.sendgrid, n8n-nodes-base.slack, n8n-nodes-base.errortrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Mychel Garzon.
Original n8n.io sourceStop compiling your weekly business report by hand. Let automation pull the numbers, and let Claude write the narrative.
Every Monday morning, this workflow fetches last week's revenue from Stripe, pipeline data from Notion, and operational metrics from Google Sheets aggregates everything into a single structured dataset, hands it to Claude Sonnet 4 for executive analysis, and delivers a styled HTML report to your inbox before you've had your first coffee.
The workflow runs in five sequential stages:
1. Trigger & Date Setup Fires every Monday at 08:00. Computes last week's date window in your configured business timezone using Luxon, outputting ISO timestamps, Unix epochs, and milliseconds so every downstream node speaks the same time format without conversion.
2. Data Collection Fetches from three sources in sequence:
3. Aggregation Normalises all three sources into a single structured item: gross and net revenue, refunds, transaction count, total and probability-weighted pipeline value, deal count by stage, and all operational KPIs. Every field has a safe fallback so missing data never crashes the report.
4. AI Executive Narrative Passes the aggregated metrics to Claude Sonnet 4 with a structured prompt requesting three paragraphs: revenue performance, pipeline health, and operational highlights with a forward-looking observation. Temperature is set to 0 for consistent, professional tone on every run.
5. Report Build & Delivery Assembles a styled HTML email with KPI cards, a pipeline stage breakdown table, and the AI narrative embedded inline. Sends via SendGrid, then fires a Slack message to your chosen channel with a one-line summary of net revenue and new deal count.
has_more is false, the report always reflects the full week, not just the first 100 chargesREPORT_TIMEZONE once and every date window, label, and timestamp respects your business timezone automaticallyN/A rather than crashing the workflowSTRIPE_SECRET_KEY environment variableNOTION_API_KEY and NOTION_DEALS_DB_ID environment variablesGSHEETS_SPREADSHEET_ID, GSHEETS_SHEET_NAME, and GSHEETS_LAST_ROW_RANGE environment variablesREPORT_EMAIL_FROM, REPORT_EMAIL_TO, and REPORT_ALERT_EMAIL environment variablesSLACK_CHANNEL_ID environment variableREPORT_TIMEZONE environment variable (e.g., Europe/Helsinki defaults to UTC if not set)Aggregate All MetricsClaude: Write Executive Narrative to change the number of paragraphs, the tone, or the specific metrics Claude should prioritizeBuild HTML Report to add your company logo, brand colors, or additional KPI sectionsThis catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Generate a weekly business metrics report with Stripe, Notion, Sheets, Claude, SendGrid, and Slack |
|---|---|
| Complexity | advanced |
| Nodes | 19 |
| Categories | Document Extraction, AI Summarization |
| Author | Mychel Garzon |
| Published | 18 May 2026 |
Use the JSON export at /data/workflows/15791/15791.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Stop compiling your weekly business report by hand. Let automation pull the numbers, and let Claude write the narrative. Every Monday morning, this workflow fetches last week's revenue from Stripe,...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Document Extraction, AI Summarization use case.