Refund Created
Receive refund.created after activation. Each partial refund is a separate event with its own amount; creation does not confirm funds have reached the customer.
Workflow template
Notify Slack when a Stripe refund is created, including partial refunds. Send the refund ID, individual amount in minor units, currency, event ID and live mode without implying completed settlement.
How it works
Receive refund.created after activation. Each partial refund is a separate event with its own amount; creation does not confirm funds have reached the customer.
Post refund ID, individual amount, currency, event ID and livemode as the FastHook bot, with a reminder to review Stripe. Disable mrkdwn and link/media previews; status and timestamp are not included.
The result
Stripe refund created Refund ID: re_example_slack_refund This refund amount (minor units): 1000 Currency: eur Event ID: evt_example_slack_refund Live mode: false Review the current refund status in Stripe; creation does not confirm arrival in the customer account.
Fictional EUR sandbox refund. The notice contains no status field, event timestamp or Stripe URL. It reports the amount of this refund, not a cumulative refunded total.
Before activation
Choose Stripe sandbox for the first test and retain refund.created as the source. Existing refunds and later status updates are outside this workflow.
Connect Slack and Browse to a channel where FastHook can post. Review access to refund IDs and amounts, and retain plain text with link and media previews disabled.
Activate, wait for Connected and inspect a new sandbox refund notice. Compare the original amount, currency, IDs and Live mode=false. Use Stripe itself to review current progress before drawing a delivery conclusion.
One partial refund is one notice. Two separate partial refunds produce two notices with their own amounts. The template does not report the payment’s accumulated refunded amount or merge events by payment.
The amount is unconverted minor units. 1000 EUR or USD means 10.00, while 1000 JPY means 1000. The action preserves the source amount and currency without conversion. No status or timestamp is mapped into this message.
Creation is not settlement confirmation. The recipe does not issue refunds or observe subsequent status updates. Contacts, card data, instructions email, metadata and destination details are excluded. Old refunds are not imported; manual reruns can send another notice.
No. It shows the individual refund amount from each refund.created event. Two partial refunds produce separate notices rather than one accumulated total.
Check Stripe. The message does not map status or timestamp, and later updates are not synchronized. Creation alone does not confirm receipt by the customer.
It is not converted. Source minor units are preserved: 1000 is 10.00 for EUR or USD, and 1000 for JPY. Read the recorded currency with the value.
No. It sends an internal Slack creation notice only. Historical refunds and later outcomes are not imported; manual reruns can duplicate messages.
Notify your team when a Stripe invoice becomes paid.
View template →Notify your team when a Stripe subscription actually ends.
View template →Notify your team when a Stripe subscription is created, including trial subscriptions.
View template →Alert your team when a Stripe PaymentIntent payment attempt fails.
View template →Notify your team when a Stripe PaymentIntent succeeds.
View template →Notify your team when a customer is created in Stripe.
View template →