Send a Slack alert to the team for each Explodely chargeback
Each time a chargeback happens on an Explodely sale, this workflow posts an alert to a Slack channel, so the people who handle disputes and refunds know about it without checking Explodely.
Explodely
Slack2 steps Setup ~5 min Used on 1.7k sites Free to import
What this workflow does
A chargeback is money leaving your account, and there is usually a window to respond with evidence. If the alert only reaches the account owner's inbox, the rest of the team may hear about it too late. This workflow puts every Explodely chargeback in front of the team in Slack.
The Explodely trigger is Chargeback, which fires when a chargeback happens. Details from the sale become values to map. The Slack step then runs Send Channel Message and posts to the #channel you choose, with the message text you build from those values.
Each chargeback gives one message. Nothing changes in Explodely, and the workflow does not dispute or refund anything; it only tells people. Task History keeps a record of every run with the data Explodely sent, which is useful if someone asks when an alert went out.
Finance channel for a digital product seller
Every Explodely chargeback posts to #finance, where the bookkeeper notes it and the owner decides whether to dispute.
Support checks the customer history
The support lead sees the alert in Slack, looks up the buyer's tickets and emails, and gathers evidence for the dispute response.
Affiliate fraud watch
Seeing chargebacks one by one in the same channel helps a vendor notice when several come from the same product.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Explodely ChargebackFires when a chargeback happens on one of your Explodely sales. Connect Explodely; the details Explodely sends about the sale become data for the Slack alert.
- Slack Send Channel Message
Posts a chargeback alert to the Slack #channel you pick. Connect Slack, choose the channel and write the text with the Explodely values your team needs.
What you need
- FlowMatticCore
- Explodely 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.
- Want refunds and cancelled rebills in the same channel? Build sister workflows on Explodely's Refund and Rebill Cancelled triggers, each with its own Slack step.
- Alerting one finance person rather than a channel? Swap in Slack's Send Direct Message action. Chargeback alerts for a private channel need Send Private Channel Message instead.
- Log each chargeback in Google Sheets too by adding an Add New Row step after Slack, so you have a list to total at month end.
Questions about this workflow
Does the workflow dispute the Explodely chargeback?
No. The workflow tells your team about the Explodely chargeback and does nothing more. Responding to the chargeback still happens in Explodely or with your payment processor.
Which Explodely details can the Slack alert show?
Whatever Explodely includes in the chargeback event, which you map into the message text. Check a test run in Task History to see the exact values.
Will refunds trigger this Slack alert as well?
No. The trigger is Chargeback only. Explodely refunds have their own trigger, which you can use in a second workflow.
More Notifications & Alerts 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