All templates

Automated Marina Failed Autopay Recovery Follow-Up

Every morning, WebRun opens Molo and finds any autopay transactions that failed since the previous run. It drafts a polite recovery email for each affected boater and posts your billing team a Slack list with the boater name, amount, and reason code so they can act before the balance ages.

Runs on WebRun · Strict Lockdown policy
Every day at 8:00 AM WebRunorchestrates each step
1 Molo find failed autopay transactions
2 Gmail draft payment recovery emails
3 Slack alert billing team with failure list
In short

How do I automatically follow up on failed autopay charges at my marina?

WebRun checks Molo every morning for autopay transactions that failed since the previous run. It drafts a polite payment recovery email for each affected boater in Gmail and posts your billing team a Slack alert listing every failed account with the reason code and escalation flags for repeat declines. No email reaches a boater without staff review.

  • Every failed autopay is caught and queued for recovery the same morning
  • Billing team sees failure reasons and escalation flags in Slack before the balance ages
  • No recovery email reaches a boater without explicit staff approval

Built for marina billing staff · marina managers · boatyard administrators · yacht club treasurers

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 app.getmolo.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Molo - find failed autopay transactions
    getmolo.com
    WebRun in Molo: find failed autopay transactions
    WebRun opens Molo to find failed autopay transactions.
    • Open Molo and navigate to the payment processing or accounts receivable section
    • Filter for autopay transactions that failed or declined since yesterday
    • Capture each boater's name, slip number, failed amount, failure reason code, and number of prior attempts

    Done when Every failed autopay transaction since yesterday is identified with amount and failure reason.

  3. 2
    Gmail - draft payment recovery emails
    gmail.com
    WebRun in Gmail: draft payment recovery emails
    WebRun opens Gmail to draft payment recovery emails.
    • Draft a polite payment recovery email for each affected boater explaining the declined charge and asking them to update their payment method or contact the office
    • Tailor the message tone for first-time failures versus repeat declines
    • Save every email as a Gmail draft. Do not send until your billing team has reviewed and approved the message

    Done when A review-ready Gmail recovery draft exists for every boater with a failed autopay since yesterday.

  4. 3
    Slack - alert billing team with failure list
    slack.com
    WebRun in Slack: alert billing team with failure list
    WebRun opens Slack to alert billing team with failure list.
    • Post a failed autopay alert to the marina billing Slack channel with the list of affected accounts
    • Include boater name, slip number, amount, failure reason, and number of prior attempts
    • Flag any account with three or more consecutive failures for escalated follow-up

    Done when Billing team has today's failed autopay list in Slack with escalation flags for repeat failures.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.getmolo.com
ScheduleRuns automatically on this cadence
Every day at 8:00 AM
DeliveryHow each run's result reaches you
Failed payment alert · Slack
OutputWhat each run produces - Gmail recovery drafts queued for billing team review plus a Slack alert listing all failed autopay accounts with escalation flags.
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 email boaters about a failed charge without our approval?

No. Every recovery email is saved as a Gmail draft for your billing team to review first. Nothing reaches a boater until a staff member approves and sends the message.

What if the autopay was retried and succeeded before the morning run?

WebRun reads the current transaction status in Molo at run time. If a charge resolved overnight, it will not appear in the failed list or generate a draft.

How does it handle repeat failures on the same account?

Accounts with three or more consecutive declines are flagged in the Slack alert for escalation so your billing team knows to reach out more directly before the balance grows.

Put this on autopilot.

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