Append successful payment to the register
Append one or more rows after an existing table.
→
Ready-made Workflow
Log successful Stripe payments in Google Sheets
Record successful Stripe PaymentIntents in Google Sheets, including payments without an invoice. Append Values writes PaymentIntent ID, Amount received (Stripe minor units), Currency, Event created (Unix seconds), Live mode and Event ID into columns A-F. Connect Stripe and Google Sheets, then browse to a spreadsheet and worksheet. Headers are optional: an empty worksheet works immediately. Listens only for payment_intent.succeeded. Includes its own fictional English Leipzig sandbox example with German characters. Uses amount_received, not the requested amount: 4900 EUR minor units means 49.00 EUR, while 4900 JPY means 4900 JPY. Values use RAW input and preserve numbers and sandbox flags. Failed, pending and canceled payments do not trigger this workflow. Existing payments, later refunds, disputes and bank payouts are not imported or synchronized. Payment success does not mean funds have reached your bank. Customer contacts, card details, client secrets and metadata are not copied. This template does not charge customers or manage invoice collection. Test with Stripe sandbox first; Live mode false identifies test data. Manual reruns can duplicate rows. This is a payment event register, not a net revenue or settlement report.
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.
Google Sheets
Connect your own Google Sheets account and review the provider settings used by this Workflow.
Explore connected apps
Related Workflow templates
Stripe · Google Sheets
Log new Stripe customers in Google Sheets
Keep a customer register in Google Sheets when a new customer is created in Stripe. Append Values writes Customer ID, Name, Email, Created (Unix seconds), Live mode and Event ID into columns A-F in that order. Connect Stripe and Google Sheets, then browse to the destination spreadsheet and worksheet. Headers are optional: an empty worksheet works immediately, or add your own header row. Includes a fictional English sandbox customer with German characters. The instant trigger listens only for customer.created events after activation; existing customers and later edits are not imported or synchronized. A customer record does not mean a payment or subscription was created. Name and email may be blank. Values use RAW input, so names starting with an equals sign remain text. No payment details, addresses, tax IDs or metadata are copied. Use a private worksheet: customer names and emails are visible to everyone who can access it. Test with a fictional customer in Stripe sandbox first; Live mode distinguishes sandbox from live events.
- 1. Stripe · Customer Created
- 2. Google Sheets · Append customer to the register
Stripe · Google Sheets
Log paid Stripe invoices in Google Sheets
Record paid Stripe invoices in Google Sheets with one row per invoice.paid event. Append Values writes Invoice ID, Amount paid (Stripe minor units), Currency, Event created (Unix seconds), Live mode and Event ID into columns A-F. Connect Stripe and Google Sheets, then browse to a spreadsheet and worksheet. Headers are optional: an empty worksheet works immediately. Includes its own fictional English Frankfurt invoice example. Values use RAW input and preserve numeric amounts, zero values and sandbox flags. Amounts are not converted or divided by 100: 1900 EUR minor units means 19.00 EUR, while 1900 JPY means 1900 JPY. Paid invoices can include zero-value invoices, customer balance and payments recorded outside Stripe; a row is not proof of a new card charge or bank payout. Only new invoice.paid events after activation are recorded. Existing invoices, later edits, refunds, drafts and open invoices are not synchronized. Customer names, emails, card details, metadata, invoice PDFs and hosted invoice links are not copied. Test with Stripe sandbox first; Live mode false identifies test data. Manual reruns can duplicate rows. This is an event register, not a complete accounting ledger.
- 1. Stripe · Invoice Paid
- 2. Google Sheets · Append paid invoice to the register
Stripe · Google Sheets
Log failed Stripe payments in Google Sheets
Record each failed Stripe PaymentIntent payment attempt in Google Sheets. Append Values writes PaymentIntent ID, Attempted amount (Stripe minor units), Currency, Event created (Unix seconds), Live mode and Event ID into columns A-F. Connect Stripe and Google Sheets, then browse to a spreadsheet and worksheet. Headers are optional: an empty worksheet works immediately. Listens only for payment_intent.payment_failed. Includes its own fictional English Hannover sandbox example with German characters. Amounts use the attempted amount, not amount received: 2900 EUR minor units means 29.00 EUR, while 2900 JPY means 2900 JPY. Values use RAW input and preserve numbers and sandbox flags. A failed attempt is not necessarily a permanent failure; a later attempt can succeed. Separate failed attempts on the same payment can produce separate rows. Successful, pending and canceled payments do not trigger this workflow. Existing payments and later outcomes are not imported or synchronized. Customer contact information, card details, client secrets, metadata and raw error objects are not copied. This template does not retry charges, contact customers, issue refunds or manage invoice collection. Test with Stripe sandbox first; Live mode false identifies test data. Manual reruns can duplicate rows. This is an attempt register, not a current payment-status report.
- 1. Stripe · Payment Intent Payment Failed
- 2. Google Sheets · Append failed payment attempt to the register
Stripe · Google Sheets
Log new Stripe refunds in Google Sheets
Record newly created Stripe refunds in Google Sheets, including partial refunds. Append Values writes Refund ID, This refund amount (Stripe minor units), Currency, Event created (Unix seconds), Live mode, Event ID and Status at creation into columns A-G. Connect Stripe and Google Sheets, then browse to a spreadsheet and worksheet. Headers are optional: an empty worksheet works immediately. Listens only for refund.created. Includes its own fictional English Köln sandbox example with German characters. Two partial refunds produce separate rows containing their own amounts, not the accumulated refunded total. For EUR and USD, 1000 minor units means 10.00; for JPY, 1000 means 1000. Values use RAW input and preserve numbers and sandbox flags. Refund creation does not confirm funds have reached the customer. Status is a snapshot at creation, not the current status; review Stripe for subsequent pending, failed, canceled or completed outcomes. Existing refunds and later updates are not imported or synchronized. Customer contacts, card details, instructions email, metadata and destination details are not copied. This template does not issue refunds or contact customers. Test with Stripe sandbox first; Live mode false identifies test data. Manual reruns can duplicate rows. This is a refund creation register, not a settlement report.
- 1. Stripe · Refund Created
- 2. Google Sheets · Append new refund to the register
Questions
Template FAQ
Does the template copy someone else's credentials?
No. FastHook creates a disconnected Draft. Connect your own Stripe, Google Sheets 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.