Stripe · 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 · 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
