Notify the team about a failed payment
Send text, Block Kit content, attachments, or a thread reply to a channel.
→
Ready-made Workflow
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.
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.