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