Automated GoCardless Failed Payment Alerts
Every hour, WebRun opens GoCardless, checks the day's direct debit collections for failures, posts the failed list to your finance Telegram, and texts you through Twilio if the failure rate spikes above your usual pattern.
How do I get alerted when GoCardless payments start failing?
WebRun checks GoCardless every hour for failed direct debit collections, posts the failed list to Telegram, and texts you through Twilio if the failure rate spikes above your usual pattern. It never retries a payment itself, so your team sees failures fast while a spike in cancellations gets your direct attention.
- Failed collections surface within the hour, not at week's end
- A genuine spike gets a direct text instead of getting lost in a list
- Routine, isolated failures stay in Telegram without paging you
Built for subscription businesses · finance teams · billing operations · SaaS finance managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
manage.gocardless.comin a real browser with your saved login - no setup, no API keys. -
1
GoCardless - check for failed collections
- Open GoCardless and pull today's collection attempts
- Filter to any marked failed or cannot pay
- Note the customer, amount, and failure reason for each
Done when Every failed collection today is captured with its reason.
-
2
Telegram - post the failed list
telegram.org
WebRun opens Telegram to post the failed list. - Post the failed collections list to the finance channel
- Include the customer, amount, and reason for each
- Leave retry decisions to the team
Done when The finance channel has today's failed collections.
-
3
Twilio - text you on a spike
twilio.com
WebRun opens Twilio to text you on a spike. - Compare today's failure rate to your recent average
- Send a text only if the rate crosses your threshold
- Stay quiet when failures are within the usual range
Done when You're texted only when the failure rate spikes.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it retry the failed payment itself?
No. WebRun never sends a payment, issues a refund, or transfers funds on its own. It only reads collection status and alerts you, leaving any retry to you and GoCardless.
How is a spike defined?
It compares today's failure rate to your recent average from live GoCardless data, so the Twilio text only fires when failures are genuinely running high.
Does every single failure get texted to me?
No. Individual failures post to Telegram for the team to see. The Twilio text is reserved for when the overall failure rate spikes.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.