Block 1 - Log Transaction
- Type / Role
- n8n-nodes-base.googleSheets - googleSheets
- Config choices
- Version 4.7
This workflow is provided as-is. Please review and test before using in production.
This n8n template demonstrates how to automate the followup when your customer completes a checkout in Stripe by emailing a receipt, logging the transaction, and sending an internal notification. S...
n8n-nodes-base.googlesheets, n8n-nodes-base.gmail, n8n-nodes-base.stripetrigger, n8n-nodes-base.wait, n8n-nodes-base.slack, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Mark Hansen.
Original n8n.io sourceThis n8n template demonstrates how to automate the followup when your customer completes a checkout in Stripe by emailing a receipt, logging the transaction, and sending an internal notification.
See the video.
This workflow is for small to medium sized organizations using Stripe for payment processing and looking for a simple way to automate communication and logging that needs to happen post-checkout.
The workflow is triggered when a Stripe checkout is completed and again when Stripe creates an invoice. Checkout and invoice details are logged to a Google Sheet. A Slack message is sent to a channel where RevOps receive notifications about new sales. Lastly, a personalized email is sent to the customer with a link for downloading their receipt.
Edit the two Stripe trigger nodes to enter your credentials. Create a Google Sheet named Payments with two tabs: transactions and invoices and the columns as shown in this example. Edit the three Google Sheets nodes to enter your credentials. The Gmail node also needs the credentials of the account that you want emails to come from. Lastly, enter credentials into the Slack node for the user that you want to be shown as posting Stripe transaction notifications. The Slack node is configured to send notifications to the revops channel, but you can change that to be whatever channel you want to use.
Use your Stripe sandbox to test the workflow. In your sandbox, create a payment link that you can use to create the checkouts that will trigger the workflow. Make sure that your payment link has the option checked to create a post-payment invoice PDF. This will trigger the Invoice Created node.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Followup Stripe checkouts with Gmail receipts, internal Slack, and Sheets logs |
|---|---|
| Complexity | intermediate |
| Nodes | 13 |
| Categories | CRM |
| Author | Mark Hansen |
| Published | 02 Oct 2025 |
Use the JSON export at /data/workflows/9173/9173.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
This n8n template demonstrates how to automate the followup when your customer completes a checkout in Stripe by emailing a receipt, logging the transaction, and sending an internal notification. S...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your CRM use case.