Stripe · Discord
Send new Stripe customers to a Discord channel
Post a Discord notification when a customer is created in Stripe. Connect Stripe and Discord, wait for the Stripe source to show Connected, then choose a Discord text channel. The instant trigger listens only for customer.created events from the connected Stripe account; existing customers and later updates are not imported. Each message contains the customer name, email, Stripe customer ID and live-mode flag. New customers do not necessarily represent a payment or subscription. No payment details, addresses, tax IDs, descriptions or metadata are forwarded. User, role and everyone mentions are disabled, so customer text cannot trigger Discord notifications accidentally. Test with a fictional customer in Stripe sandbox first and choose a channel whose members may see customer names and email addresses. Name and email may be empty when Stripe does not provide them. Includes its own fictional German customer example with no real customer data.
- 1. Stripe · Customer Created
- 2. Discord · Notify the customer channel
View template →Use templateStripe · Notion
Create Notion review pages for failed Stripe payments
Keep a review page in Notion for each failed Stripe PaymentIntent attempt. Select an accessible parent with Browse; the new child page records PaymentIntent ID, attempted amount in Stripe minor units, currency, event Unix seconds, live mode and Event ID, followed by three follow-up prompts. Each failed attempt creates its own page, including repeat failures for the same PaymentIntent. Check current status in Stripe before taking action: a later retry may already have succeeded. Amounts are not converted; 2900 EUR means 29.00 EUR, while 2900 JPY means 2900 JPY. Includes a fictional English Würzburg workshop example with German characters. Earlier failures are not imported and later success does not update or close the page. Customer contacts, card details, client secrets, raw errors and metadata are excluded. Pages inherit parent access. Creates child pages, not database items or invoice dunning schedules. This workflow does not retry payments, issue refunds or contact customers. Test in Stripe sandbox first. Manual reruns can duplicate pages.
- 1. Stripe · Payment Intent Payment Failed
- 2. Notion · Create the failed payment review page
View template →Use templateStripe · Trello
Create Trello review tasks for new Stripe refunds
Put new Stripe refunds in a Trello review queue. Choose a board and list with Browse; each refund.created event creates a card with Refund ID, individual refund amount in Stripe minor units, currency, status at creation, event time, live mode and Event ID, followed by four manual review prompts. Two partial refunds create separate tasks with their own amounts, not the payment's cumulative refunded total. Creation can be pending and does not confirm that the customer has received the money; check current status in Stripe. For currency minor units, 700 EUR means 7.00 EUR, while 700 JPY means 700 JPY. Includes its own fictional English Köln workshop example with German characters. Earlier refunds and later status changes are not imported or synchronized. Customer contacts, card details, refund reasons, instructions and metadata are excluded. Cards inherit board visibility. The workflow logs refunds without issuing refunds, contacting customers or closing cards automatically. Test in Stripe sandbox first. Manual reruns can duplicate tasks.
- 1. Stripe · Refund Created
- 2. Trello · Create the refund review task
View template →Use templateStripe · Trello
Create Trello offboarding tasks for canceled Stripe subscriptions
Queue a Trello offboarding review when a Stripe subscription actually ends. Select a board and list with Browse; each customer.subscription.deleted event creates a card containing Subscription ID, final status, currency, event Unix seconds, live mode and Event ID, plus four review prompts. Scheduling cancel_at_period_end only emits an update and does not create a card until termination. Includes a fictional English Bremen studio ended-trial example with German characters. Ended trials and paid subscriptions are included without assuming voluntary churn or lost revenue. The event time is the termination notification, not the earlier cancellation request. Multiple prices are supported without inferring MRR from the first item. Review current Stripe details, outstanding invoices and your retention policy before changing access. Existing cancellations and later edits are not imported or synchronized; onboarding cards are not updated. Customer contacts, cancellation feedback/comments, private descriptions, payment details and metadata are excluded. Cards inherit board visibility. The template creates a review task; it does not cancel subscriptions, issue refunds, revoke access or contact customers. Test in Stripe sandbox first. Manual reruns can duplicate cards.
- 1. Stripe · Customer Subscription Deleted
- 2. Trello · Create the subscription offboarding task
View template →Use templateStripe · 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
View template →Use templateStripe · Trello
Create Trello review cards for successful Stripe payments
Give successful Stripe payments a place in your Trello review queue. Choose a board and list with Browse; each new payment_intent.succeeded event creates a card with PaymentIntent ID, Amount received (Stripe minor units), Currency, Event created (Unix seconds), Live mode and Event ID, followed by four manual review prompts. Includes payments without an invoice and its own fictional English Dresden workshop example with German characters. Uses amount_received rather than the requested amount: 4900 EUR minor units means 49.00 EUR, while 4900 JPY means 4900 JPY. Failed, pending and canceled payments do not create cards. Check Stripe and delivery requirements before approving fulfillment; payment success does not confirm settlement in your bank. Existing payments and later refunds, disputes and payouts are not imported or synchronized. Customer contacts, card details, client secrets and metadata are excluded. Cards inherit board visibility, so select a board appropriate for payment records. This workflow does not charge customers, issue refunds, fulfill orders or send messages. Test with a fictional Stripe sandbox payment first; Live mode false identifies test data. Manual reruns can duplicate cards.
- 1. Stripe · Payment Intent Succeeded
- 2. Trello · Create the successful payment review task
View template →Use templateStripe · Notion
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.
- 1. Stripe · Payment Intent Succeeded
- 2. Notion · Create the payment review page
View template →Use templateStripe · Notion
Create Notion 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
View template →Use templateStripe · 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
View template →Use templateStripe · Trello
Create Trello onboarding tasks for new Stripe subscriptions
Start a manual onboarding queue when a Stripe subscription is created. Connect Stripe and Trello, then browse to your board and list. Each card records Subscription ID, status at creation, currency, event Unix seconds, live mode and Event ID, followed by a short onboarding review checklist. Listens only for customer.subscription.created and includes its own fictional English Stuttgart studio trial example. Trials and incomplete subscriptions also create cards: subscription creation is not proof of payment or permission to grant access. Verify current subscription status and your onboarding policy in Stripe before provisioning anything. A subscription may contain multiple prices; this task does not infer a total, paid revenue or MRR from the first item. Existing subscriptions, renewals, status changes and cancellations are not imported or synchronized. No customer contacts, payment details or metadata are copied. Cards inherit board visibility. The workflow does not create subscriptions, charge customers, grant access or send messages. Test in Stripe sandbox first; Live mode false identifies test events. Manual reruns can duplicate cards.
- 1. Stripe · Customer Subscription Created
- 2. Trello · Create the subscription onboarding task
View template →Use templateStripe · Trello
Create Trello cards for paid Stripe invoices
Turn newly paid Stripe invoices into Trello review tasks. Connect Stripe and Trello, then browse to your board and list. Each card records Invoice ID, amount paid in original Stripe minor units, currency, event Unix time, live-mode flag and Event ID, plus a short handoff checklist. Listens only for invoice.paid and includes an independent fictional English Hamburg invoice example. Paid invoices can include zero-value invoices, customer balance or payments recorded outside Stripe; a card is not proof of a new card charge, payout or an order ready to ship. Verify the invoice and delivery requirements in Stripe before fulfilling anything. Amounts are not converted: 1900 EUR means 19.00 EUR, while 1900 JPY means 1900 JPY. Only future events create cards. Existing invoices, edits, refunds and disputes are not imported or synchronized, and recurring paid invoices can create separate tasks. No customer contacts, addresses, payment details, invoice PDFs, hosted links or metadata are copied. Cards inherit board visibility. The workflow does not charge customers, send messages, ship orders or issue refunds. Test in Stripe sandbox first; Live mode false identifies test events. Manual reruns can duplicate cards.
- 1. Stripe · Invoice Paid
- 2. Trello · Create the paid invoice review task
View template →Use templateStripe · Google Sheets
Log canceled Stripe subscriptions in Google Sheets
Maintain a cancellation register when Stripe subscriptions actually end. Append Values saves Subscription ID, Final status, Currency, Event created (Unix seconds), Live mode and Event ID in columns A-F. Choose a spreadsheet and worksheet through Browse; a blank worksheet works without headers. Listens only for customer.subscription.deleted and includes an independent fictional English München canceled-trial example. Setting cancel_at_period_end merely schedules cancellation and sends an update; the row arrives when the subscription ends. Covers ended trials and paid subscriptions without assuming customer intent or calculating lost revenue from the first price. The event timestamp records the end notification, not the earlier cancellation request. RAW preserves numbers and boolean sandbox flags. This is a future-event register, not an update to existing subscription rows or a historical import. Review Stripe for the cancellation cause and outstanding invoices. No customer contacts, cancellation comments, payment details or metadata are copied. Choose worksheet access carefully. Test in Stripe sandbox first; Live mode false identifies test events. The workflow does not cancel subscriptions, issue refunds, revoke access or send messages. Manual reruns can duplicate rows.
- 1. Stripe · Customer Subscription Deleted
- 2. Google Sheets · Append the ended subscription to the cancellation register
View template →Use templateStripe · Google Sheets
Log new Stripe subscriptions in Google Sheets
Keep a creation register of Stripe subscriptions in Google Sheets, including trials. Append Values writes Subscription ID, Status at creation, 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. An empty worksheet works immediately; column headers are optional. Listens only for customer.subscription.created and includes its own fictional English Düsseldorf trial example. Status is a snapshot at creation: a trialing or incomplete subscription is not proof of payment. Subscriptions can contain several prices, so this register does not treat the first price as a total or calculate MRR. RAW input preserves numbers and boolean sandbox flags. Existing subscriptions, renewals, status changes and cancellations are not imported or synchronized. No customer contacts, payment details or metadata are copied. Choose a worksheet with appropriate access. Test with Stripe sandbox first; Live mode false identifies test events. This workflow does not create subscriptions, charge customers, grant access or send messages. Manual reruns can duplicate rows.
- 1. Stripe · Customer Subscription Created
- 2. Google Sheets · Append the new subscription to the register
View template →Use templateStripe · Trello
Create Trello follow-up cards for failed Stripe payments
Create a Trello follow-up card when a Stripe PaymentIntent payment attempt fails. Connect Stripe and Trello, then browse to a board and list for payment review. The card contains the PaymentIntent ID, attempted amount in original Stripe minor units, currency, event creation time in Unix seconds, event ID and live-mode flag, followed by a short review checklist. Assign an owner in Trello and check the latest payment status in Stripe before contacting anyone: a later retry may already have succeeded. Each new failed-attempt event creates a separate card, even for the same PaymentIntent. Existing failures are not imported, and later success does not update or close the card. Amounts are not converted: 2900 EUR means 29.00 EUR, while 2900 JPY means 2900 JPY. This does not retry charges, issue refunds, send customer messages or implement invoice retry schedules. No customer contact details, card data, client secrets, raw error messages or metadata are copied. Cards inherit board visibility. Includes a fictional English Nürnberg workshop example. Test in Stripe sandbox first; Live mode false identifies sandbox events. Manual reruns can create duplicate cards.
- 1. Stripe · Payment Intent Payment Failed
- 2. Trello · Create the payment review card
View template →Use templateStripe · 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
View template →Use templateStripe · 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
View template →Use templateStripe · Google Sheets
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.
- 1. Stripe · Payment Intent Succeeded
- 2. Google Sheets · Append successful payment to the register
View template →Use templateStripe · 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
View template →Use templateStripe · 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
View template →Use templateStripe · Slack
Send Slack alerts for paid Stripe invoices
Notify your team when a Stripe invoice becomes paid. Connect Stripe and Slack, browse to your billing channel, then publish. Uses invoice.paid and sends the Invoice ID, invoice amount paid in Stripe minor units, currency, event ID and live-mode flag. Includes subscription renewal invoices and one-off invoices. For EUR and USD, 1900 minor units means 19.00; for JPY, 1900 means 1900. Paid invoices can include zero-value invoices, customer balance and invoices marked paid outside Stripe, so this alert is not proof of a new card charge or bank payout. Includes an independent fictional München invoice example. Review the invoice in Stripe for payment details. No customer contact information, payment details, hosted invoice links, PDF links or metadata are forwarded. This workflow does not create invoices, collect payments, or import existing paid invoices. Drafts and open invoices do not trigger it. Test with Stripe sandbox first; Live mode false identifies test events. Manual workflow reruns can duplicate notifications.
- 1. Stripe · Invoice Paid
- 2. Slack · Notify the team about a paid invoice
View template →Use templateStripe · Slack
Send Slack alerts for canceled Stripe subscriptions
Notify your team when a Stripe subscription actually ends. Connect Stripe and Slack, browse to your customer-success channel, then publish. Uses customer.subscription.deleted and sends the Subscription ID, status, currency, event ID and live-mode flag. Scheduling cancellation at the end of a period only updates the subscription and does not trigger this workflow; the alert arrives when the subscription ends. Includes an independent fictional München canceled-trial example. Covers cancellations after trials as well as paid subscriptions without claiming lost revenue or a customer-requested cancellation. Review the subscription in Stripe for the cause and any outstanding invoices. This workflow does not cancel subscriptions, issue refunds, revoke access, or import past cancellations. No customer contact information, cancellation comments, payment details or metadata are forwarded. Test with Stripe sandbox first; Live mode false identifies test events. Manual workflow reruns can duplicate notifications.
- 1. Stripe · Customer Subscription Deleted
- 2. Slack · Notify the team about an ended subscription
View template →Use templateStripe · Slack
Send Slack alerts for new Stripe subscriptions
Notify your team when a Stripe subscription is created, including trial subscriptions. Connect Stripe and Slack, browse to your subscriptions channel, then publish. Uses customer.subscription.created and sends the Subscription ID, status at creation, currency, event ID and live-mode flag. A new subscription can be trialing or incomplete: creation is not proof of payment and this workflow does not grant customer access. Includes an independent fictional München trial subscription example. Supports subscriptions with multiple prices without presenting a single price as the total. No customer contact information, payment details or metadata are forwarded. This workflow does not create subscriptions, import existing subscriptions, or notify about renewals, updates and cancellations. Test with Stripe sandbox first; Live mode false identifies test events. Manual workflow reruns can duplicate notifications.
- 1. Stripe · Customer Subscription Created
- 2. Slack · Notify the team about a new subscription
View template →Use templateStripe · Slack
Send Slack alerts for new Stripe refunds
Notify your team when a new Stripe refund is created, including partial refunds. Connect Stripe and Slack, browse to a payment operations channel, then publish. Uses refund.created and sends the Refund ID, the amount of that individual refund in Stripe minor units, currency, event ID and live-mode flag. For EUR and USD, 1000 minor units means 10.00; for JPY, 1000 means 1000. Two partial refunds produce separate alerts for their own amounts, not the accumulated refunded total. Includes an independent fictional EUR sandbox refund example. Refund created does not mean funds have reached the customer: review its current status in Stripe. This workflow does not issue refunds or track subsequent pending, failed, canceled or completed status updates. No customer contact information, card details, instructions email, metadata or destination details are forwarded. Test with Stripe sandbox first; Live mode false identifies test events. Existing refunds are not imported, and manual workflow reruns can duplicate notifications.
- 1. Stripe · Refund Created
- 2. Slack · Notify the team about a new refund
View template →Use templateStripe · Slack
Send Slack alerts for failed Stripe payments
Alert your team when a Stripe PaymentIntent payment attempt fails. Connect Stripe and Slack, browse to your payment alerts channel, then publish. Listens only for payment_intent.payment_failed and sends the PaymentIntent ID, attempted amount in Stripe minor units, currency, event ID and live-mode flag. For EUR and USD, 2900 minor units means 29.00; for JPY, 2900 means 2900. Includes its own fictional failed EUR sandbox payment example. Review the payment in Stripe before contacting a customer: a failed attempt is not necessarily a permanently failed payment, and a later retry can succeed. Each new failed-attempt event can generate another alert. Successful, pending and canceled payments do not trigger this workflow. It does not retry charges, issue refunds, contact customers or track invoice-specific retry schedules. No card details, client secrets, customer contact information or raw error objects are forwarded. Test in Stripe sandbox first; Live mode false identifies test events. Manual workflow reruns can duplicate notifications.
- 1. Stripe · Payment Intent Payment Failed
- 2. Slack · Notify the team about a failed payment
View template →Use templateStripe · Slack
Send Slack alerts for successful Stripe payments
Notify your team when a Stripe PaymentIntent succeeds. Connect Stripe and Slack, browse to a channel where the FastHook bot can post, then publish. The trigger listens only for payment_intent.succeeded. Each plain-text message contains the PaymentIntent ID, amount received in Stripe minor units, currency, event ID and live-mode flag. For EUR and USD, 4900 minor units means 49.00; for zero-decimal currencies such as JPY, 4900 means 4900. Amounts are not converted between currencies. Includes its own fictional EUR sandbox payment example. Pending, failed and canceled payments do not send this alert. Existing payments, later refunds, disputes and bank payouts are not synchronized. Payment success does not mean funds have reached your bank. No card details, client secrets, customer contact information or metadata are forwarded. Choose a channel appropriate for payment notifications and test with Stripe sandbox first. Live mode false identifies test events. Manual reruns can send another notification.
- 1. Stripe · Payment Intent Succeeded
- 2. Slack · Notify the payment alerts channel
View template →Use templateStripe · Google Drive
Create Google Drive folders for new Stripe customers
Prepare a document folder when a new customer is created in Stripe. Connect Stripe and Google Drive, optionally choose a writable parent folder, then publish. Without a parent, folders are created in My Drive. The folder name includes the Stripe Customer ID and customer name; the ID remains even when the name is blank. Includes its own fictional sandbox customer with German characters. Only customer.created events received after activation are processed. Creating a customer does not confirm payment or a subscription. Existing customers and later edits are not imported or synchronized. This creates an empty folder; it does not copy invoices, payment details, email addresses, tax IDs or metadata, or attach the folder to Stripe. Folder access follows its destination; sharing permissions are not changed. Test with a fictional sandbox customer first. Manually rerunning an event can create another folder with the same name.
- 1. Stripe · Customer Created
- 2. Google Drive · Create customer document folder
View template →Use templateStripe · 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
View template →Use templateStripe · Telegram Bot
Send Telegram alerts for new Stripe customers
Receive a Telegram notification when a new customer is created in Stripe. Connect Stripe and Telegram, select the destination chat, and keep the prepared customer name, email and ID mappings. The instant trigger listens only for customer.created events from the connected Stripe account. Includes its own fictional English sandbox customer with German characters. Creating a customer does not confirm a payment or subscription. Existing customers and later updates are not imported. Name and email may be empty. The message includes the live-mode flag to distinguish sandbox events. No payment details, addresses, tax IDs or metadata are forwarded. Choose a chat whose members may see customer names and email addresses; the Telegram bot must be able to post there. Test with a fictional Stripe sandbox customer first.
- 1. Stripe · Customer Created
- 2. Telegram Bot · Notify the customer alerts chat
View template →Use templateStripe · HubSpot
Create HubSpot contacts for new Stripe customers
Create one HubSpot contact from the email address on each new Stripe customer. Connect Stripe and HubSpot, then activate the workflow. Customers without an email address are skipped. Use a valid unique email; invalid or existing emails may fail, and this template does not upsert or update contacts. The customer.created event is the only trigger. Creating a customer does not confirm a payment or subscription. No marketing subscriptions are configured. Historical customers are not imported and later customer updates are not synchronized. Includes a fictional English sandbox example for Lina Müller using a valid example.com address. Only email is copied; names, phone numbers, addresses, metadata and payment details are not transferred. Test with a fictional Stripe sandbox customer first.
- 1. Stripe · Customer Created
- 2. HubSpot · Create CRM contact
View template →Use templateStripe · Trello
Create Trello onboarding cards for new Stripe customers
Start a customer onboarding card in Trello when a new customer is created in Stripe. Each card includes the customer name, email, customer ID, event ID and live-mode flag. Connect Stripe and Trello, then browse to the destination board and list. Includes a fictional English sandbox example with German characters. Only customer.created events received after activation are processed; existing customers and later edits are not imported or synchronized. A new customer record does not mean a payment or subscription exists. Customer ID remains in the card title even if the name is blank, and name or email may be empty. No payment details, addresses, tax IDs or metadata are copied. Choose a private board appropriate for customer contact information. Test with a fictional Stripe sandbox customer first; Live mode false identifies sandbox events.
- 1. Stripe · Customer Created
- 2. Trello · Create a customer onboarding card
View template →Use templateStripe · 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
View template →Use templateStripe · Slack
Send Slack alerts for new Stripe customers
Notify your team when a customer is created in Stripe. Connect Stripe and Slack, choose a channel where the FastHook bot can post, and keep the prepared customer name, email and ID mappings. The instant trigger listens only for customer.created events from the connected Stripe account. Includes its own fictional English customer with German characters. New customers do not necessarily represent a payment or a subscription. Existing customers and later updates are not imported. Customer name and email are shared with everyone in the selected Slack channel; choose an appropriate channel. No payment details, addresses, tax IDs or metadata are forwarded. Test with a fictional customer in Stripe sandbox first; the message includes the live-mode flag so test events can be distinguished. Customer name and email may be empty if they were not provided in Stripe.
- 1. Stripe · Customer Created
- 2. Slack · Notify the customer onboarding channel
View template →Use template
