Send a Slack alert to finance when a PayU payment fails
Each time a PayU payment fails, this workflow posts a message to the Slack channel your finance team reads, carrying the payment details you choose to include from the PayU event.
PayU
Slack2 steps Setup ~5 min Used on 1.5k sites Free to import

What this workflow does
A failed card payment is easy to miss when it only shows up in the PayU dashboard. Finance hears about it days later, if at all, and the customer may think the purchase went through. This workflow puts each failure in front of your finance people in the Slack channel they already watch.
The PayU trigger, Payments Failed, fires when a payment fails. FlowMattic receives the payment data from that event and hands it to Slack. The Send Channel Message action then posts to the channel you pick, using a message you write and fill with values from the PayU event, such as the amount or the customer's details.
There is no Filter, so every failed payment produces one Slack message. Successful, refunded and disputed payments don't start this workflow, because the trigger listens only for failures. Task History keeps a record of each run, so you can check what PayU sent and what was posted.
Finance channel for an online store
Your store takes card payments through PayU. Each failure lands in #finance, so someone can contact the buyer and offer another way to pay.
Spotting a gateway problem early
Several failure messages arriving close together in Slack point to a wider issue worth raising with PayU, rather than one customer's card.
Subscription or invoice payments
When a client's payment through PayU fails, the account manager sees it in Slack and can send a fresh payment link before access lapses.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
PayU Payments FailedFires when a payment fails in your PayU account. The data PayU sends about that payment becomes available to map into the Slack message.
Slack Send Channel MessageSends the failure notice to whichever Slack channel you select. Write the text and insert values from the PayU event, then run a test so you can see which payment fields PayU provides.
What you need
- FlowMatticCore
- PayU 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.
- Add a Filter after the PayU trigger that continues only when the payment amount PayU sends is greater than a figure you set, so small failures stay out of the channel. Blank amounts count as 0 and won't pass.
- Pick a channel your finance team reads, not a general one. For a private finance channel, swap the action for Slack's Send Private Channel Message.
- Add a Google Sheets Add New Row step after Slack to keep a running log of failed PayU payments you can review each month.
Questions about this workflow
Does a failed PayU payment trigger one Slack message or several?
One per failure event PayU reports. If a customer retries and fails again, that second failure is a new event and posts another message.
Can the PayU failure alert go to a private Slack channel?
The Send Channel Message action posts to a channel you pick. For a private channel, use Slack's Send Private Channel Message action, and to reach one person, use Send Direct Message.
Which PayU payment details can I put in the message?
Whatever PayU includes in the failure event. Trigger a test failure, or wait for a real one, then open the Slack step and pick from the fields FlowMattic captured.
Will successful PayU payments post to Slack too?
No. The trigger is Payments Failed, so only failed payments start a run. Use a separate workflow with a different PayU trigger if you want other events posted.
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


