Notify the team about an ended subscription
Send text, Block Kit content, attachments, or a thread reply to a channel.
→
Ready-made Workflow
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.
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.
Slack
Connect your own Slack account and review the provider settings used by this Workflow.
Questions
Template FAQ
Does the template copy someone else's credentials?
No. FastHook creates a disconnected Draft. Connect your own Stripe, Slack 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.