Handle payments differently across small, mid, and large amount tiers
When a Stripe charge succeeds, a Router sorts it into a large, mid or small tier by amount. Large payments alert your team in Slack and get a personal email, and the other tiers get their own thank-you.
Stripe
Router
Slack
Email6 steps Setup ~12 min Used on 2.5k sites Finance Free to import
What this workflow does
A one-size receipt treats a customer who just paid a large invoice the same as one who bought a small add-on. This workflow lets you respond to each payment in proportion: bigger payments get a team heads-up and a warmer note, smaller ones a short thanks.
A run begins each time Stripe records a successful new charge. A Router then checks the charge amount on three routes. Large covers amounts greater than 2000. Mid covers amounts greater than 200 and less than 2001. Small covers amounts less than 201. The ranges don't overlap, so each charge follows exactly one route.
On the Large route, a Slack message posts the amount and the payer's email to a channel so someone can follow up, and the customer gets an email saying a team member will be in touch. Mid and Small each send one thank-you email with its own wording.
Stripe reports amounts in the smallest currency unit, such as cents, so 2000 here means 20.00 in a two-decimal currency. Check the amount in a test run and change the thresholds to the tiers you mean. FlowMattic compares these values as whole numbers, and a blank amount counts as 0, so it would take the Small route.
Personal follow-up on big orders
A B2B supplier gets a Slack ping for every large card payment, so an account manager can call the buyer the same day while the customer receives a note saying to expect it.
Different thanks for donors by gift size
A nonprofit taking donations through Stripe sends major donors a warmer message and a team alert, while smaller gifts get a quick thank-you.
Course sales with upsell tiers
An online course seller treats full-program purchases as the large tier and single-lesson buys as small, with wording that fits each.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Stripe New ChargeStarts on every successful new Stripe charge. The charge amount and payer details are passed to the Router and the email steps.
- Router 3 paths
Checks the charge amount on three routes: Large for more than 2000, Mid for more than 200 and less than 2001, Small for less than 201. Each charge matches one route only.
- Slack Send Channel Message
On the Large route, posts a message to a Slack channel with the amount and the payer's email, asking the team to send a personal note. Pick the channel after import.
Email Send EmailAlso on the Large route, emails the payer a thank-you for their order and says a team member will follow up personally. Edit the wording to match how you handle large clients.
- Email Send Email
On the Mid route, sends the payer a plain thank-you for their payment. The subject and body are written in the template and can be changed before you go live.
- Email Send Email
On the Small route, sends a brief email confirming the payment was received. This route also catches charges with no amount, since a blank value compares as 0.
What you need
- FlowMatticCore
- Stripe AccountAccount
- Slack AccountAccount
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- Run a small test charge and look at the amount in Task History. If it arrives in cents, set the Router thresholds in cents too, for example 50000 for a 500.00 large tier.
- Check the email field in a test run before going live. If the charge has no payer email, map the billing email Stripe returns instead, or the three emails have no address to go to.
- Keep route conditions that can't both match when you add a fourth tier, such as splitting Mid into two ranges with an upper and lower bound each, because a Router runs every route whose condition matches.
- Use Slack's Send Direct Message action on the Large route instead of the channel message if one account manager owns all large payments.
Questions about this workflow
Can one Stripe charge get more than one email from this Router?
No. The three ranges don't overlap: above 2000, from 201 to 2000, and 200 or below. Every charge matches exactly one route. If you change a threshold, keep the ranges from overlapping.
Is 2000 dollars or cents in the Stripe amount condition?
Stripe reports the charge amount in the smallest unit of the currency, such as cents. Check the amount value in a test run, then set the thresholds to what you consider large, mid and small.
Does the trigger fire for failed or refunded Stripe charges?
No. FlowMattic describes this event as a new charge that is created and successful. Failed attempts don't start a run, and refunds of a past charge don't start it either.
Which Slack channel gets the large payment alert?
You pick it yourself when you set up the Send Channel Message step. Pick a channel where the people who follow up with customers will see it.
More Finance & Payments workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted