Create the payment review page
Create a titled page under an existing Notion page.
→
Ready-made Workflow
Create Notion review pages for successful Stripe payments
Keep a Notion payment review page for each successful Stripe PaymentIntent, including payments without an invoice. Browse to a parent page; each child page records PaymentIntent ID, Amount received (Stripe minor units), Currency, Event created (Unix seconds), Live mode and Event ID, followed by a Payment review section and three reconciliation prompts. Listens only for payment_intent.succeeded; failed, pending and canceled payments do not create pages. Uses amount_received rather than the requested amount: 4900 EUR minor units means 49.00 EUR, while 4900 JPY means 4900 JPY. Check the currency before interpreting amounts. Includes its own fictional English Stuttgart workshop example with German characters. These are child pages, not database items. Existing payments and later refunds, disputes, invoice changes and bank payouts are not imported or synchronized. Success does not prove settlement in your bank or net revenue. Customer contacts, card details, client secrets and metadata are excluded. Pages inherit parent access. The template does not charge customers, issue refunds, fulfill orders or send messages. Test in Stripe sandbox first; Live mode false identifies test data. Manual reruns can duplicate pages.
Use this templateCreates a new Draft · no credentials copied
What gets copied
The working graph, not another user's secrets
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Before activation
Connect your accounts in the Draft
Stripe
Connect your own Stripe account and review the provider settings used by this Workflow.
Notion
Connect your own Notion account and review the provider settings used by this Workflow.
Explore connected apps
Related Workflow templates
Stripe · Notion
Create Notion onboarding pages for new Stripe customers
Create a customer onboarding page in Notion when a new Stripe customer is created. Connect Stripe and Notion, then browse to an accessible parent page. Each child page title includes the customer name, email and Stripe customer ID, followed by Onboarding, Notes and Follow-up sections ready for your team. Customer ID identifies the page even when name or email is missing. Includes its own fictional English sandbox example with German characters. Only customer.created events after activation are processed; historical customers and later edits are not imported or synchronized. Creating a customer does not confirm a payment or subscription. No payment details, addresses, tax IDs, descriptions or metadata are copied. Access follows the selected Notion parent, so choose one appropriate for customer contact information. This creates child pages, not database rows. Test with a fictional Stripe sandbox customer first.
- 1. Stripe · Customer Created
- 2. Notion · Create customer onboarding page
Stripe · Notion
Create Notion pages for paid Stripe invoices
Keep a Notion child page for each new invoice.paid event from Stripe. Connect Stripe and Notion, then browse to an accessible parent page. Each page title contains the invoice number and Stripe invoice ID; its prepared content records Invoice ID, Amount paid in Stripe minor units, Currency, Event created in Unix seconds, Live mode and Event ID, followed by Reconciliation notes. This gives your team a place to review an invoice event and add internal notes. Includes a fictional English Frankfurt workshop example. Only events received after activation are processed; existing invoices, later edits and refunds are not imported or synchronized. Amounts stay in original minor units: 1900 EUR means 19.00 EUR, while 1900 JPY means 1900 JPY. Zero-value invoices are supported. Invoice Paid can also mean customer balance or a payment recorded outside Stripe; it does not prove a new card charge or bank payout. Customer contact information, billing addresses, card details, invoice PDFs, hosted invoice URLs and metadata are not copied. Pages inherit access from the selected Notion parent. This creates child pages, not database rows or a full accounting ledger. Test with a fictional Stripe sandbox invoice first. Manual reruns can create another page.
- 1. Stripe · Invoice Paid
- 2. Notion · Create the paid invoice review page
Stripe · Notion
Create Notion onboarding pages for new Stripe subscriptions
Create a dedicated Notion onboarding page when a Stripe subscription is created. Connect Stripe and Notion, then browse to a parent page your Notion integration can access. Each child page contains Subscription ID, status at creation, currency, event Unix seconds, live mode and Event ID, plus editable Onboarding notes and three prepared review prompts. This gives an onboarding owner a place to record an agreed plan before provisioning access. Listens only for customer.subscription.created and includes its own fictional English Leipzig studio trial example. Trials and incomplete subscriptions also produce pages: creation is not proof of payment or entitlement. Review current subscription status in Stripe and apply your access policy before granting anything. Subscriptions may have multiple prices; no first-item total or MRR is inferred. This is a creation snapshot, not a synchronized subscriber database. Existing subscriptions, renewals, later changes and cancellations are not imported or synchronized. Customer contacts, private descriptions, payment details and metadata are not copied. Pages inherit parent access. The workflow does not create subscriptions, charge customers, send messages or grant access. Test in Stripe sandbox first; Live mode false identifies test events. Manual reruns can create duplicate pages.
- 1. Stripe · Customer Subscription Created
- 2. Notion · Create the subscription onboarding page
Stripe · Notion
Create Notion offboarding review pages for canceled Stripe subscriptions
Open a Notion cancellation review page when a Stripe subscription actually ends. Choose a parent page through Browse; each child page records Subscription ID, final status, currency, event Unix seconds, live mode and Event ID, followed by an editable Cancellation review section and three offboarding prompts. This gives an owner a place to check outstanding obligations and record a decision before changing access. The trigger listens only for customer.subscription.deleted. Setting cancel_at_period_end schedules cancellation and emits an update; the page is created when the subscription ends. Includes its own fictional English Frankfurt ended-trial example. Ended trials and paid subscriptions are included without assuming voluntary churn or lost revenue. The event timestamp identifies the termination notification, not an earlier cancellation request. Review current Stripe details and your retention policy before acting. Multiple prices are supported without inferring MRR from the first item. This creates child pages, not database items or updates to onboarding pages. Existing cancellations and later changes are not imported or synchronized. Customer contacts, cancellation feedback and comments, payment details and metadata are excluded. Pages inherit parent access. The workflow does not cancel subscriptions, issue refunds, revoke access or contact customers. Test in Stripe sandbox first; Live mode false marks test data. Manual reruns can duplicate pages.
- 1. Stripe · Customer Subscription Deleted
- 2. Notion · Create the subscription offboarding review page
Stripe · Notion
Create Notion review pages for new Stripe refunds
Track each new Stripe refund in a Notion child page under a parent selected with Browse. Records the refund ID, individual refund amount in Stripe minor units, currency, status at creation, event time, live mode and event ID, followed by three review prompts. Two partial refunds create separate pages with their individual amounts, not the payment's cumulative refunded total. A refund.created event can be pending; creation does not confirm that the customer has received the money. Check current status in Stripe. Interpret minor units using the currency: 1000 EUR means 10.00 EUR, while 1000 JPY means 1000 JPY. Includes a fictional English Düsseldorf workshop example with German characters. Uses child pages, not database items. Earlier refunds and later status changes are not imported or synchronized. Customer contacts, card details, refund instructions, reasons and metadata are excluded. Pages inherit parent access. Logs refunds without issuing refunds or sending messages. Test in Stripe sandbox first. Manual reruns can duplicate pages.
- 1. Stripe · Refund Created
- 2. Notion · Create the refund review page
Questions
Template FAQ
Does the template copy someone else's credentials?
No. FastHook creates a disconnected Draft. Connect your own Stripe, Notion accounts before activation.
Can I change the Steps and mappings?
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
What is copied into my workspace?
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
When does the Workflow start running?
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.