Tell your team on Slack or Teams about big or failed payments
Post a message when a payment is over an amount you choose, or when a payment fails.
- Time:
- 5 minutes
- Plan:
- Free. Free covers one gateway. A Pro project adds more sources (up to 10).
- Status:
- Beta
- Code:
- None
Beta: tested against sample payloads, not yet verified on a live account.
payment.received (amount ≥ ₦1m) → slack: post message
The problem
Sales wants to know when a big customer pays. Support wants to know when a payment fails, before the customer calls.
What you get
- A Slack or Teams message for each payment over your amount.
- A separate message for each failed payment.
- No code. Filters do the work.
Steps
- 1
Connect Slack
Open your workspace and go to Connections. Find Slack and click Connect. Paste an incoming webhook URL from your Slack app. For Teams, paste the channel webhook URL. Hooksnode keeps the keys and tokens encrypted. Members can see that the connection exists, but not its secrets.
- 2
Add your payment gateway as a source
In your project, go to Sources, click Add source and pick A business tool. Choose one of Paystack, Flutterwave or Moniepoint (Monnify). Free covers one gateway. A Pro project adds more sources (up to 10). Copy the webhook URL that Hooksnode shows and paste it into the webhook settings of your gateway dashboard. Hooksnode checks the gateway signature on every request and refuses forged events.
- 3
Add a Slack action for big payments
Go to Destinations and click Run a tool action. Pick Slack and Post a message. Set the event types to payment.received. Then open the destination and add this filter. Amounts are in kobo, so ₦1,000,000 is 100000000:
{ "data.status": "succeeded", "data.amount.amount_minor": {"gte": 100000000} } - 4
Add a second action for failed payments
Add one more Slack action with the event type payment.failed. It needs no filter.
Tips
- Filters support eq, neq, in, nin, gt, gte, lt, lte, contains, prefix, suffix, matches and exists. Group them with all, any and not.
- Hooksnode checks a filter when you save it, so a typo does not silently drop events.
- The same pattern works for bank alerts, invoices and stock events.