Create the successful payment review task
Create a card in a Trello list.
→
Ready-made Workflow
Create Trello review cards for successful Stripe payments
Give successful Stripe payments a place in your Trello review queue. Choose a board and list with Browse; each new payment_intent.succeeded event creates a card with PaymentIntent ID, Amount received (Stripe minor units), Currency, Event created (Unix seconds), Live mode and Event ID, followed by four manual review prompts. Includes payments without an invoice and its own fictional English Dresden workshop example with German characters. Uses amount_received rather than the requested amount: 4900 EUR minor units means 49.00 EUR, while 4900 JPY means 4900 JPY. Failed, pending and canceled payments do not create cards. Check Stripe and delivery requirements before approving fulfillment; payment success does not confirm settlement in your bank. Existing payments and later refunds, disputes and payouts are not imported or synchronized. Customer contacts, card details, client secrets and metadata are excluded. Cards inherit board visibility, so select a board appropriate for payment records. This workflow does not charge customers, issue refunds, fulfill orders or send messages. Test with a fictional Stripe sandbox payment first; Live mode false identifies test data. Manual reruns can duplicate cards.
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.
Trello
Connect your own Trello account and review the provider settings used by this Workflow.
Explore connected apps
Related Workflow templates
Stripe · Trello
Create Trello onboarding cards for new Stripe customers
Start a customer onboarding card in Trello when a new customer is created in Stripe. Each card includes the customer name, email, customer ID, event ID and live-mode flag. Connect Stripe and Trello, then browse to the destination board and list. Includes a fictional English sandbox example with German characters. Only customer.created events received after activation are processed; existing customers and later edits are not imported or synchronized. A new customer record does not mean a payment or subscription exists. Customer ID remains in the card title even if the name is blank, and name or email may be empty. No payment details, addresses, tax IDs or metadata are copied. Choose a private board appropriate for customer contact information. Test with a fictional Stripe sandbox customer first; Live mode false identifies sandbox events.
- 1. Stripe · Customer Created
- 2. Trello · Create a customer onboarding card
Stripe · Trello
Create Trello follow-up cards for failed Stripe payments
Create a Trello follow-up card when a Stripe PaymentIntent payment attempt fails. Connect Stripe and Trello, then browse to a board and list for payment review. The card contains the PaymentIntent ID, attempted amount in original Stripe minor units, currency, event creation time in Unix seconds, event ID and live-mode flag, followed by a short review checklist. Assign an owner in Trello and check the latest payment status in Stripe before contacting anyone: a later retry may already have succeeded. Each new failed-attempt event creates a separate card, even for the same PaymentIntent. Existing failures are not imported, and later success does not update or close the card. Amounts are not converted: 2900 EUR means 29.00 EUR, while 2900 JPY means 2900 JPY. This does not retry charges, issue refunds, send customer messages or implement invoice retry schedules. No customer contact details, card data, client secrets, raw error messages or metadata are copied. Cards inherit board visibility. Includes a fictional English Nürnberg workshop example. Test in Stripe sandbox first; Live mode false identifies sandbox events. Manual reruns can create duplicate cards.
- 1. Stripe · Payment Intent Payment Failed
- 2. Trello · Create the payment review card
Stripe · Trello
Create Trello cards for paid Stripe invoices
Turn newly paid Stripe invoices into Trello review tasks. Connect Stripe and Trello, then browse to your board and list. Each card records Invoice ID, amount paid in original Stripe minor units, currency, event Unix time, live-mode flag and Event ID, plus a short handoff checklist. Listens only for invoice.paid and includes an independent fictional English Hamburg invoice example. Paid invoices can include zero-value invoices, customer balance or payments recorded outside Stripe; a card is not proof of a new card charge, payout or an order ready to ship. Verify the invoice and delivery requirements in Stripe before fulfilling anything. Amounts are not converted: 1900 EUR means 19.00 EUR, while 1900 JPY means 1900 JPY. Only future events create cards. Existing invoices, edits, refunds and disputes are not imported or synchronized, and recurring paid invoices can create separate tasks. No customer contacts, addresses, payment details, invoice PDFs, hosted links or metadata are copied. Cards inherit board visibility. The workflow does not charge customers, send messages, ship orders or issue refunds. Test in Stripe sandbox first; Live mode false identifies test events. Manual reruns can duplicate cards.
- 1. Stripe · Invoice Paid
- 2. Trello · Create the paid invoice review task
Stripe · Trello
Create Trello onboarding tasks for new Stripe subscriptions
Start a manual onboarding queue when a Stripe subscription is created. Connect Stripe and Trello, then browse to your board and list. Each card records Subscription ID, status at creation, currency, event Unix seconds, live mode and Event ID, followed by a short onboarding review checklist. Listens only for customer.subscription.created and includes its own fictional English Stuttgart studio trial example. Trials and incomplete subscriptions also create cards: subscription creation is not proof of payment or permission to grant access. Verify current subscription status and your onboarding policy in Stripe before provisioning anything. A subscription may contain multiple prices; this task does not infer a total, paid revenue or MRR from the first item. Existing subscriptions, renewals, status changes and cancellations are not imported or synchronized. No customer contacts, payment details or metadata are copied. Cards inherit board visibility. The workflow does not create subscriptions, charge customers, grant access or send messages. Test in Stripe sandbox first; Live mode false identifies test events. Manual reruns can duplicate cards.
- 1. Stripe · Customer Subscription Created
- 2. Trello · Create the subscription onboarding task
Stripe · Trello
Create Trello offboarding tasks for canceled Stripe subscriptions
Queue a Trello offboarding review when a Stripe subscription actually ends. Select a board and list with Browse; each customer.subscription.deleted event creates a card containing Subscription ID, final status, currency, event Unix seconds, live mode and Event ID, plus four review prompts. Scheduling cancel_at_period_end only emits an update and does not create a card until termination. Includes a fictional English Bremen studio ended-trial example with German characters. Ended trials and paid subscriptions are included without assuming voluntary churn or lost revenue. The event time is the termination notification, not the earlier cancellation request. Multiple prices are supported without inferring MRR from the first item. Review current Stripe details, outstanding invoices and your retention policy before changing access. Existing cancellations and later edits are not imported or synchronized; onboarding cards are not updated. Customer contacts, cancellation feedback/comments, private descriptions, payment details and metadata are excluded. Cards inherit board visibility. The template creates a review task; it does not cancel subscriptions, issue refunds, revoke access or contact customers. Test in Stripe sandbox first. Manual reruns can duplicate cards.
- 1. Stripe · Customer Subscription Deleted
- 2. Trello · Create the subscription offboarding task
Questions
Template FAQ
Does the template copy someone else's credentials?
No. FastHook creates a disconnected Draft. Connect your own Stripe, Trello 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.