Stripe webhooks charge.succeeded, charge.refunded, and invoice.paid hit n8n. The customer email is looked up in QuickBooks; if missing, a customer record is created from Stripe metadata. Every successful charge writes a sales receipt against the right income account based on the Stripe product tag. Refunds post a credit memo linked to the original receipt. Any charge over your threshold (default $1k) pings #revenue in Slack. A Notion ledger holds the full audit trail with the raw Stripe event JSON attached. Month-end close drops from 4 days to 2 hours.
Tool-interchange map · every layer is swappable
Payment → Books · tool-interchange map
Every layer is swappable · the architecture is not
What it does
Stripe webhooks charge.succeeded, charge.refunded, and invoice.paid hit n8n in real time. The customer email is looked up in QuickBooks; if no record exists, one is created from the Stripe metadata (email, name, address, tax ID).
Every successful charge writes a sales receipt against the right income account based on the Stripe product tag · so your revenue reporting stays clean by product line without manual tagging. Refunds post a credit memo linked to the original receipt, which means your aging report never lies. Any charge over your threshold (default $1,000) pings #revenue in Slack with the plan and MRR delta.
A Notion ledger holds the full audit trail with the raw Stripe event JSON attached, so if your accountant ever asks “what happened on June 14 at 3pm”, the answer is one click away. Month-end close typically drops from four days to two hours.
Real-world use cases
Bootstrapped SaaS founder with 400 paying customers
Every month you close your own books. It takes a full day and you dread it.
Before
You export a Stripe CSV, open QuickBooks, manually create sales receipts for any new customers, reconcile refunds by hand, and flag yourself notes about what MRR changed and why.
After
Books are live-updated. The only thing you do at month-end is read the Notion ledger for context on anomalies. Close drops from 8 hours to 90 minutes of review.
Agency charging 20 retainer clients
Retainer invoices go out on the 1st, payments land across the next 10 days, and reconciling which payment matches which invoice is tedious.
Before
Your ops manager spends half a day a week matching Stripe payouts to QuickBooks invoices and chasing late payers manually.
After
Each Stripe charge auto-matches to its QuickBooks invoice by invoice ID. Late payers (no charge by day 10) trigger a polite reminder email. Your ops manager spends 15 minutes a week on this.
What changes for your team
Real runs, observed
Trigger
charge.succeeded event: $499 Pro plan, existing customer, product tag "saas-pro"
What landed
QuickBooks sales receipt created against the customer, income coded to "SaaS Revenue · Pro", Notion ledger row written, no Slack ping (under threshold)
Time
3 seconds
Trigger
charge.refunded event for a $2,400 annual plan
What landed
QuickBooks credit memo posted and linked to the original receipt, customer flag in HubSpot updated to "churned-refund", Slack ping to #revenue with the customer name and reason field
Time
5 seconds
Default tool stack
Sample prompts
Time + scope
2 to 3 days
To ship
Fixed
Pricing model
Included
Source JSON
14 days
Tweak window
Live in these engines
Related templates
A webhook takes a LinkedIn URL or email. Perplexity pulls 90 days of company news, funding, and headcount shifts. Claude Sonnet scores against your ICP JSON and writes a 3-sentence opener referencing one specific signal. Smartlead queues the email at 9:45am local; Expandi fires the LinkedIn touch 36 hours later. End-to-end: under 3 minutes per prospect.
View →Template · 2 to 3 daysFireflies emits the transcript.ready webhook. n8n passes the transcript to Claude Sonnet with a strict JSON schema (decisions, actions with owners and due dates, blockers, follow-ups). Owners resolve by fuzzy-matching speaker names to your Notion people DB. Each action writes a row in the project page; Slack pings every assignee with a deep link. P95 latency call-ends to Slack-ping: 72 seconds.
View →Template · 2 to 3 daysCalendly fires the invitee.created event. Clay enriches the email (company, headcount, tech stack, LinkedIn). Claude Haiku picks the right rep from your round-robin config using tier rules (enterprise → enterprise AE, under 10 seats → PLG rep). HubSpot gets the contact plus deal in one upsert. The rep Slack DM lands with the prospect company, 3-bullet context, and the two most recent LinkedIn posts. All inside 18 seconds.
View →Ready to ship this?
Book a call. I review your stack, confirm the fit, and we start the same week.