TL;DR

Invoice Auto-Documentation is a finance workflow that chains Stripe + Notion to automate a common task. Every Stripe invoice is automatically documented in a Notion database with amount, customer, and payment status. Once configured, it runs through Claude Code, Cursor, Windsurf or any MCP-compatible AI agent.

💳📝

FinanceBeginner

Invoice Auto-Documentation

Every Stripe invoice is automatically documented in a Notion database with amount, customer, and payment status.

8 min setup, continuous documentation2 MCPs required

How it works

💳Stripe

📝Notion

Automated

1Stripe webhook fires on invoice.paid2Extract customer and amount from event3Create Notion database entry+2 more steps

Hostable — runs in your browser2/2 MCPs hosted

Run with MCPizy

New

Execute this recipe in your browser — no local install, no Claude Code. Streams results live.

Whitelisted MCPs: perplexity, notion, anthropic, openai, tavily, firecrawl, coingecko, stripe, slack, github, gitlab, linear, resend, sendgrid, elevenlabs, shopify, sentry, posthog, supabase-mcp, context7, deepwiki~4k tokens · ~$0.012 est.

Why this combo?

Stripe holds the ground truth of your revenue; Notion is where your team does financial planning. Connecting them means your finance database updates itself in real time — no copy-pasting from Stripe dashboards into spreadsheets at month end.

Without this workflow

Download CSV from Stripe, paste into Notion manually at month end, fix formatting, realize you missed some invoices, redo it.

With MCPizy

Every paid invoice creates a Notion entry automatically. Month-end review is just reading a page that wrote itself.

Business value

Concrete ROI — not marketing fluff.

Time saved

Eliminates human copy-paste errors in revenue reporting — investors get accurate numbers, not rounded estimates
Non-technical stakeholders (ops, sales) self-serve revenue data in Notion without learning Stripe dashboard
Historical invoice audit trail lives in your shared workspace — critical for due diligence and SOC2

Workflow steps

1
Stripe webhook fires on invoice.paid
2
Extract customer and amount from event
3
Create Notion database entry
4
Tag with month, plan, and customer tier
5
Update monthly revenue aggregation page

Use cases

Auto-log every paid invoice into a Notion revenue tracker
Tag invoices by plan tier for MRR segmentation reports
Build a live customer payment history page in Notion
Track failed payments and churn signals in a shared Notion board

MCPs required

💳

Stripe

Stripe MCP Server

View

📝

Notion

Notion MCP Server

View

Agent prompt (copy into Claude Code)

This prompt is the workflow. Paste into Claude Code, Cursor, or Windsurf.

You are an invoice-documentation agent. Runs on Stripe webhook events.

On invoice.paid:
1. Call stripe.retrieve_invoice(id) to get amount_paid, currency, customer, lines[]
2. Call stripe.retrieve_customer(customer_id) to get email, name, metadata.plan, metadata.tier
3. Call notion.notion-create-pages in database REVENUE_DB_ID with properties:
   - Invoice: invoice.number
   - Amount: amount_paid / 100
   - Currency: currency
   - Customer: customer.email
   - Plan: metadata.plan
   - Tier: metadata.tier
   - Date: created (ISO)
   - Status: "Paid"
4. Call notion.notion-update-page on the monthly rollup page (property: MRR += amount)

On invoice.payment_failed: same but Status="Failed" + tag with retry count.

Trigger & credentials

How this workflow fires and what env vars you need.

.env.example

WebhookTrigger

POST /webhook/stripe (Stripe Dashboard → Developers → Webhooks, events: invoice.paid, invoice.payment_failed)

💳Stripe· 2 vars

STRIPE_SECRET_KEYGet key

Your Stripe secret API key

e.g. sk_live_...

STRIPE_WEBHOOK_SECRETGet key

Webhook signing secret

e.g. whsec_...

📝Notion· 3 vars

NOTION_API_KEYGet key

Notion internal integration token

e.g. secret_...

NOTION_REVENUE_DB_ID

Database ID for invoice log (32-char UUID)

e.g. a1b2c3d4e5f67890a1b2c3d4e5f67890

NOTION_MRR_PAGE_ID

Page ID for monthly MRR rollup

e.g. a1b2c3d4e5f67890a1b2c3d4e5f67890

One-command deploy

Install everything — MCPs, prompt, env template — in a single call.

$ mcpizy recipe install stripe-notion-invoice-docs

✓ Installs all 2 MCP servers
✓ Writes prompt to ~/.mcpizy/prompts/stripe-notion-invoice-docs.md
✓ Generates .env.example in current directory
✓ Ready to paste into Claude Code

Requires mcpizy CLI v1.1+ — install via npm i -g mcpizy.

Quick install (MCPs only)

8 min setup, continuous documentation

$ mcpizy install stripe && mcpizy install notion

More Finance recipes

💳💬

Payment Notifications

Receive a Slack message for every successful payment, failed charge, and subscription cancellation in real time.

🦎💬

Crypto Price Alerts

Monitor cryptocurrency prices and receive Slack alerts when assets cross custom thresholds or drop more than 5% in an hour.

Frequently asked questions

What is this workflow?

Invoice Auto-Documentation is a finance automation that uses Stripe + Notion together via the Model Context Protocol. Every Stripe invoice is automatically documented in a Notion database with amount, customer, and payment status.

How long does setup take?

Setup takes around 8 min setup, continuous documentation. You install the required MCP servers with `mcpizy install stripe && mcpizy install notion`, connect your accounts, and the workflow is ready to run.

What does this workflow change in practice?

Eliminates human copy-paste errors in revenue reporting — investors get accurate numbers, not rounded estimates; Non-technical stakeholders (ops, sales) self-serve revenue data in Notion without learning Stripe dashboard.

Which MCP servers do I need for this?

You need 2 MCP servers: Stripe (mcpizy install stripe), Notion (mcpizy install notion). All are installable in one command via the MCPizy CLI and configured in your `.claude.json` or `.cursor/mcp.json`.

Does this work with Claude Code, Cursor, and Windsurf?

Yes. The workflow runs with any MCP-compatible AI agent — Claude Code, Claude Desktop, Cursor, Windsurf, VS Code with Copilot, and custom agents built on the MCP SDK. The MCP servers are identical across clients; only the config file path (`.claude.json` vs `.cursor/mcp.json`) changes.

Start building this workflow

Install the required MCPs from the directory and automate this in 8 min setup.

$ mcpizy install stripe && mcpizy install notion

💳Install Stripe 📝Install Notion

Free to install. Connect your accounts and this workflow runs itself.