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