All templates
For residential cleaning companies, recurring cleaning services & maid service operators

Recover failed payments before clients go to collections

When Stripe flags a failed payment for a cleaning client, WebRun checks the Jobber record for any upcoming visits, drafts a polite card-update request for the client, and posts an alert to Slack so your team can follow up before the next appointment.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
When a payment fails WebRun
1 Stripe detect failed payment
2 Jobber check for upcoming visits
3 Gmail draft card-update request
4 Slack alert the team
Run a sample
In short

How do I automatically recover failed payments for my cleaning business?

When Stripe records a failed payment, WebRun immediately checks the client's upcoming visits in Jobber, drafts a polite card-update email held in Gmail for your approval, and alerts your billing team in Slack with the failure reason and next visit date so recovery happens before the next clean.

  • Failed payments are caught and actioned within minutes, not days
  • Clients are contacted before their next visit, reducing awkward in-person payment conversations
  • Repeat declines are flagged separately for escalation so problem accounts get extra attention

Built for residential cleaning companies · recurring cleaning services · maid service operators · commercial janitorial businesses

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens dashboard.stripe.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Stripe - detect failed payment
    stripe.com How to Automate Stripe
    WebRun in Stripe: detect failed payment
    WebRun opens Stripe to detect failed payment.
    • Detect a failed charge or declined recurring payment event in Stripe
    • Capture the client name, email, amount, and failure reason
    • Note whether this is a first failure or a repeat decline

    Done when The failed payment is identified with client details and failure context.

  3. 2
    Jobber - check for upcoming visits
    getjobber.com How to Automate Jobber
    WebRun in Jobber: check for upcoming visits
    WebRun opens Jobber to check for upcoming visits.
    • Look up the client in Jobber using the email from Stripe
    • Check for any visits scheduled in the next 7 days
    • Note the visit dates so the recovery message can reference the upcoming service

    Done when The client's upcoming visit schedule is confirmed or noted as none.

  4. 3
    Gmail - draft card-update request
    gmail.com How to Automate Gmail
    WebRun in Gmail: draft card-update request
    WebRun opens Gmail to draft card-update request.
    • Draft a polite email asking the client to update their payment details
    • Reference the upcoming visit date to create urgency without being pushy
    • Leave the email as a draft for your review before sending

    Done when One draft recovery email is ready in Gmail for your approval.

  5. 4
    Slack - alert the team
    slack.com How to Automate Slack
    WebRun in Slack: alert the team
    WebRun opens Slack to alert the team.
    • Post an alert to the billing channel with the client name, amount, failure reason, and next visit date
    • Flag repeat declines separately so they can be escalated
    • Note the draft email is waiting in Gmail for approval

    Done when The billing team has an immediate alert in Slack with full context.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
dashboard.stripe.com
ScheduleRuns automatically on this cadence
When a payment fails
DeliveryHow each run's result reaches you
Recovery draft · Gmail
OutputWhat each run produces - A draft client recovery email in Gmail and a Slack alert with the client, amount, failure reason, and next visit date.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it contact the client automatically when a payment fails?

No. The recovery email is drafted in Gmail and held for your review. You approve and send it yourself, so every client communication about a payment issue goes out with your oversight.

Does it retry the payment on the client's card?

No. WebRun only drafts the outreach and alerts your team. Any payment retry or card update must be handled by you directly in Stripe or Jobber, keeping financial actions firmly in your hands.

What if the client has no upcoming visits?

It notes the absence of upcoming visits in the Slack alert and adjusts the email draft accordingly, so the tone is appropriate for a client who is not expecting a cleaner shortly.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.