Send a Monday business metrics email from Stripe, Notion and Sheets with Claude writing the narrative in n8n
A shared n8n template pulls last week's Stripe revenue, Notion deal pipeline and a Sheets row of support numbers, has Claude write a three-paragraph summary, and emails and posts it to Slack.
Evidence: The source shows its work: steps, screenshots, code or data you can inspect.
The business problem
A founder with revenue, sales and support numbers in three places has to open each one to understand how the week went.
What was tried
A Monday 08:00 trigger works out last week's date window in your timezone. The workflow reads all Stripe charges for that window, queries a Notion deals database with a date filter, and reads the latest operations row (tickets closed, NPS, uptime) from Google Sheets. It combines them into one set of figures with fallbacks for missing values, asks Claude to write a three-paragraph narrative on revenue, pipeline and operations, builds an HTML email with KPI cards and a stage table, sends it through SendGrid and posts a one-line summary to Slack. An error trigger emails the failed step.
What was reported (not reported)
The template reports no results from real use. It shows the working structure and the settings you need to fill in.
Limitations
A template page with no usage data and no publication date (the page shows an update about five months ago). The Stripe pagination handling is the author's own statement, a fixed 350 ms delay is used to stay under Notion's rate limit, and only the latest row of the Sheets tab is read. Missing operations figures show as N/A rather than stopping the run. The narrative is written by a language model from three numbers, so check it against the figures before acting. It needs several credentials, including a Stripe secret key.
What you need
An n8n instance, Stripe, Notion and Google accounts, an Anthropic API key, a SendGrid account and a Slack channel, plus about a dozen environment variables.
Sources
- n8n workflow library (Mychel Garzon) ↗ Tutorial, publication date unknown
Source published: unknown. Last reviewed here: October 11, 2026. Spot a mistake? Tell us.
Tools in this workflow
- Claude: Writes the three-paragraph narrativeTry Claude
- Notion: Holds the deals pipeline that is readTry Notion
- Slack: Receives a one-line summary of the reportTry Slack
- Stripe: Source of last week's revenue and refundsTry Stripe
- n8n: Runs the schedule and joins the data sourcesTry n8n
Related workflows
Brief your team on every Stripe cancellation with an AI agent that checks support tickets and account history
A Tines example workflow fires on a Stripe cancellation, lets an AI agent look up the customer's support tickets and account history, and posts a structured churn brief to Slack.
Categorise and rank cancellation reasons by revenue impact before deciding what to fix, with AI help once you have 50 responses
A solo founder's step-by-step method for pulling cancellation reasons from Stripe, surveys and support tickets into one place, tagging them by theme, and ranking themes by how much revenue they cost.
Investigate a revenue dip, onboarding drop-off and user segments with Claude Code, the PostHog MCP and your interview transcripts
A product person connects Claude Code to PostHog and a folder of company context and interview transcripts, then asks it to explain a revenue dip, a funnel drop and user segments.
Turn a GA4 funnel export into three ranked conversion tests with Claude, then lower its confidence scores yourself
A CRO consultant describes exporting a GA4 funnel as a table, giving Claude the product context and constraints, and asking for the three biggest leaks with a hypothesis, change, metric and ICE or PIE score for each.