Refund Created
Receive new refund.created events, including separate partial refunds. A refund can be pending at creation, and the event does not prove customer receipt.
Workflow template
Queue new Stripe refunds for review in Trello. Create a card for each individual refund with amount, creation-status snapshot and event references plus four manual review prompts.
How it works
Receive new refund.created events, including separate partial refunds. A refund can be pending at creation, and the event does not prove customer receipt.
Create a card in your chosen list with refund ID, individual amount/currency, status at creation, event time, live mode and event ID. Add four review prompts as description text, without issuing refunds, assigning an owner or closing cards automatically.
The result
Review refund: re_example_trello_refund
New Stripe refund Refund ID: re_example_trello_refund This refund amount (Stripe minor units): 700 Currency: eur Status at creation: pending Event created (Unix seconds): 1789639200 Live mode: false Event ID: evt_example_trello_refund Refund review - Assign a review owner in Trello. - Match this refund to the original payment and order. - Check current refund status in Stripe; creation status is a snapshot, not confirmation of receipt. - Record the review decision and close this card manually once reviewed.
Fictional Köln sandbox refund. The amount is 700 source minor units and the four prompts are description text, not native checklist items. Visibility follows the selected board.
Before activation
Connect Stripe and retain Refund Created. Use a new fictional refund creation rather than an existing refund or a later status update for the first check.
Connect Trello and Browse to the destination. Review board access to refund identifiers and amounts. The written owner and closure instructions are not automatic assignments or actions.
Activate, wait for Connected and verify a sandbox refund creates the card. Compare the seven source fields, then check the current refund in Stripe before recording a decision and closing the card manually.
Partial refunds remain separate tasks. Each refund has its own amount and card, not the payment’s cumulative refunded total. Earlier refunds are not imported, later changes do not update cards and manual reruns can create duplicates.
Amount and creation status are source snapshots. 700 EUR represents 7.00 EUR, while 700 JPY represents 700 JPY. No conversion occurs. Pending at creation is not a current-status guarantee or confirmation that the customer received money.
The prompts are for human review. There is no native checklist creation, automatic assignee or card closure. The workflow does not issue refunds or contact customers. Contacts, card details, refund reasons, instructions and metadata are excluded.
No. Each refund.created event creates its own card with that refund’s amount, not a cumulative total for the payment.
No. Status is captured at creation, later changes are not synchronized and closure is manual. Check the latest state in Stripe; creation does not confirm customer receipt.
No. They are description text rather than native checklist items or automated actions. Assign an owner and record the review decision yourself; no refund or customer message is sent.
It is unchanged Stripe minor units: 7.00 EUR, or 700 JPY if the currency were JPY. The action preserves the individual source amount without conversion, and reruns can duplicate cards.
Queue a Trello offboarding review when a Stripe subscription actually ends.
View template →Give successful Stripe payments a place in your Trello review queue.
View template →Start a manual onboarding queue when a Stripe subscription is created.
View template →Turn newly paid Stripe invoices into Trello review tasks.
View template →Create a Trello follow-up card when a Stripe PaymentIntent payment attempt fails.
View template →Start a customer onboarding card in Trello when a new customer is created in Stripe.
View template →